CVSS 3.1
5.8 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:NCVE-2026-128080 OpenTelemetry JavaScript: Insertion of Sensitive Information into Log File and Exposure of Sensitive Information to an Unauthorized Actor in @opentelemetry/instrumentation-http
Medium (5.8) in open-telemetry opentelemetry-js. Fixed in @opentelemetry/instrumentation-http 0.222.0.
On this page
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.
Severity
- CWEs
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-532 Insertion of Sensitive Information into Log File - Published
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-128080 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128080?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128080?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128080 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-128080)
HTML:
<a href="https://cve.bz/cve/CVE-2026-128080"><img src="https://cve.bz/cve/badge/CVE-2026-128080.svg" alt="CVE-2026-128080"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| open-telemetry opentelemetry-js | >= 0.204.0, < 0.222.0 |
Fix and patched versions
@opentelemetry/instrumentation-http(npm): fixed in 0.222.0
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-3v2p-hm54-8qcq | npm | @opentelemetry/instrumentation-http | >=0.204.0 <0.222.0 | 0.222.0 |
Attack patterns (CAPEC)
- CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).