# CVE-2026-128080: OpenTelemetry JavaScript: Insertion of Sensitive Information into Log File and Exposure of Sensitive Information to an Unauthorized Actor in @opentelemetry/instrumentation-http


- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** DHI-ig4g-zrhb-ka44-d4ct, GHSA-3v2p-hm54-8qcq

## What is CVE-2026-128080?

CVE-2026-128080 is a medium-severity vulnerability in open-telemetry opentelemetry-js, published on 13 Nov 2026. 

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-128080?

1 open source package ship an affected version, including @opentelemetry/instrumentation-http.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `@opentelemetry/instrumentation-http` | npm | `pkg:npm/%40opentelemetry/instrumentation-http` | From 0.204.0 | 0.222.0 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `@opentelemetry/instrumentation-http` | 0.222.0 |

## How do I fix CVE-2026-128080?

Upgrade @opentelemetry/instrumentation-http to 0.222.0 or later.

## Is CVE-2026-128080 being exploited?

There is no known exploitation of CVE-2026-128080 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128080 and fix it if it is affected.

What it is: CVE-2026-128080 is a medium-severity vulnerability in open-telemetry opentelemetry-js, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128080 in the wild and no public exploit code.

Affected packages and fixed versions:
- @opentelemetry/instrumentation-http (npm): affected from 0.204.0; fixed in 0.222.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128080/ (Markdown: https://insights.sbomify.com/CVE-2026-128080/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128080
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128080
- OSV: https://osv.dev/vulnerability/CVE-2026-128080

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128080/
Summaries are generated and may contain mistakes; the official description above is the record.
