Skip to main content
VulnerabilityPublished

CVE-2026-128080: open-telemetry opentelemetry-js · Information Exposure

Affects open-telemetry opentelemetry-jsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.8 Medium : upgrade to 0.222.0 when convenient.

Data as of 13 Nov 2026, 18:47 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.8
Patch
Available – fixed in 0.222.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 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 13 Nov 2026.

What to do

Upgrade open-telemetry opentelemetry-js to 0.222.0.

Affected software

ProductAffectedFixed in
open-telemetryopentelemetry-jsAffected
  • >=0.204.0 <0.222.0
Fixed in
  • 0.222.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 0.222.0 or later of opentelemetry-js where the issue is fixed. No other mitigation is indicated or required as the vulnerability is resolved by this official fix.

Description

A vulnerability in open-telemetry's JavaScript client (opentelemetry-js) versions 0.204.0 through 0.221.x causes raw query strings from incoming HTTP requests to be recorded in tracing spans without redaction. This can expose sensitive information such as signed URLs or credentials to anyone with access to tracing backends. The issue is fixed in version 0.222.0.

References

Community reviews

Loading reviews…