Vulnerability in @opentelemetry/propagator-jaeger (CVE-2026-59892)
Summary
Vulnerability in @opentelemetry/propagator-jaeger (CVE-2026-59892). Risk of unauthorized operations or information disclosure. Exploitable via URIError. Mitigation: upgrade to 2.9.0 or later.
Original description
The description as published by the source.
OpenTelemetry JavaScript is the OpenTelemetry JavaScript client. Prior to 2.9.0, @opentelemetry/propagator-jaeger decodes incoming uber-trace-id and uberctx-* HTTP header values with decodeURIComponent() without handling decode errors, allowing an unauthenticated remote attacker to send a malformed percent-encoded value that throws an uncaught URIError and terminates a Node.js process using JaegerPropagator as the active propagator. This issue is fixed in version 2.9.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59892 has been found in @opentelemetry/propagator-jaeger.
Attackers can target a specific entry point like URIError over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade @opentelemetry/propagator-jaeger to 2.9.0 or later.
If unsure, ask your IT team or search "@opentelemetry/propagator-jaeger CVE-2026-59892" on the vendor's site.
CVE-2026-59892 (@opentelemetry/propagator-jaeger) — CWE-248 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: URIError / JaegerPropagator / OTEL_PROPAGATORS / jaeger
Patched: 2.9.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-248) exists in @opentelemetry/propagator-jaeger. Attackers reach the vulnerable code path via URIError without authentication.
Check the vendor advisory for the affected versions of @opentelemetry/propagator-jaeger. Attack surface: URIError / JaegerPropagator / OTEL_PROPAGATORS / jaeger.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.9.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@opentelemetry/propagator-jaeger' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@opentelemetry/propagator-jaeger' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@opentelemetry/propagator-jaegerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @opentelemetry/propagator-jaeger to 2.9.0ステージング環境で 2.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web github.com