Skip to main content
VulnerabilityPublished

CVE-2026-59892: open-telemetry opentelemetry-js · Uncaught Exception

Affects open-telemetry opentelemetry-jsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.9.0 soon.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.9.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade opentelemetry-js and @opentelemetry/propagator-jaeger to 2.9.0.

Affected software

ProductAffectedFixed in
open-telemetryopentelemetry-jsAffected
  • <2.9.0
Fixed in
  • 2.9.0
npm@opentelemetry/propagator-jaegerpkg:npm/@opentelemetry/propagator-jaegerOther threatsAffected
  • <2.9.0
Fixed in
  • 2.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to version 2.9.0 or later of opentelemetry-js where this issue is fixed. Patch status is confirmed by the version fix noted in the description. No other mitigations are indicated.

Description

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.

References

Community reviews

Loading reviews…