CVE
OpenTelemetry JS sensitive data leak in HTTP instrumentation spans
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 0.222.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.222.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.36% · 30th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 43/100 · provisional
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 53% of @opentelemetry/instrumentation-http downloads last week were affected versions (18.8M).npm, 35.1M downloads in the last 7 days, read Nov 14, 2026
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenTelemetry JavaScript's @opentelemetry/instrumentation-http package writes the raw query string of incoming HTTP requests into trace data, so still-valid secrets such as signed URLs can be exported to tracing backends where observability infrastructure and users with span-read access may read them. The flaw can be reached remotely over the network without logging in or any user action.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
OpenTelemetry JavaScript is the OpenTelemetry JavaScript client. From 0.204.0 until 0.222.0, @opentelemetry/instrumentation-http writes the raw query string from incoming HTTP requests to the url.query server-span attribute without applying the redactedQueryParams protection used for outgoing spans. Services receiving signed URLs or other credentials in query parameters can therefore export still-valid secrets to tracing backends, where observability infrastructure and users with span-read access may read them. The redactedQueryParams option does not protect incoming spans in affected versions. This issue is fixed in version 0.222.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach20/20@opentelemetry/instrumentation-http: 35.1M downloads a week
- Severity5.8/10CVSS 5.8
- No patch0/5No signal
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
- Would score about 48 if advisories confirm default setups are exposed
Impact
- Widely used
@opentelemetry/instrumentation-http has 35.1m weekly downloads.Source: npmjs.com
What to do
Upgrade to a fixed version: 0.222.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128080 (OpenTelemetry JavaScript: Insertion of Sensitive Information into Log File and Exposure of Sensitive Information to an Unauthorized Actor…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128080 (entry last updated 2026-11-13):
Affected:
- open-telemetry opentelemetry-js: from 0.204.0, fixed in 0.222.0
- npm package @opentelemetry/instrumentation-http: from 0.204.0, fixed in 0.222.0
Fixed versions: 0.222.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128080 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128080 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-3v2p-hm54-8qcq
- https://github.com/open-telemetry/opentelemetry-js/commit/e086dec7f9304107ef6d50b5877be88895c06aa7
- https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental/v0.222.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128080
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128080"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- open-telemetry opentelemetry-js
From 0.204.0 · fixed in 0.222.0
From 0.204.0 · fixed in 0.222.0
Fixed in 0.222.0 (released Aug 31, 2026, 74 days before disclosure).
The latest release, 0.301.2, is not affected.
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128080
Is CVE-2026-128080 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-128080?
opentelemetry-js: from 0.204.0 before 0.222.0. @opentelemetry/instrumentation-http (npm): from 0.204.0 before 0.222.0.Source: cve.now feed data
How do I fix CVE-2026-128080?
Upgrade to a fixed version: 0.222.0.Source: cve.now feed data