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.
CVE-2026-59892
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 35.2%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 10, 2026
Advisory Details (3)
Auto-updated Jul 8, 2026Denial of service in `JaegerPropagator` via unhandled exception on a malformed header · Advisory · open-telemetry/opentelemetry-js · GitHub
https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-45rx-2jwx-cxfrv2.9.0
Patch available: open-telemetry/opentelemetry-js v2.9.0
https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.9.0commit b1c196d49d54 (open-telemetry/opentelemetry-js)
Patch available: open-telemetry/opentelemetry-js experimental/v0.220.0 (contains commit b1c196d49d54)
https://github.com/open-telemetry/opentelemetry-js/commit/b1c196d49d54caae59741cca0a9d57d101d7ea88Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-11 21:23 UTCEG score recompute
- 2026-07-11 10:24 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 23:25 UTCEG score recompute
- 2026-07-10 12:25 UTCEG score recompute
- 2026-07-10 01:26 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 14:24 UTCEG score recompute
- 2026-07-09 03:24 UTCEG score recompute
- 2026-07-08 16:25 UTCEG score recompute
- 2026-07-08 16:24 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59892?
When was CVE-2026-59892 disclosed?
Is CVE-2026-59892 actively exploited?
What is the CVSS score of CVE-2026-59892?
How do I remediate CVE-2026-59892?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59892
Is Your Infrastructure Affected by CVE-2026-59892?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.