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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2026-128080: 0.36% estimated exploitation activity in the next 30 days; percentile 30.59 (FIRST EPSS, 2026-11-14). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary `@opentelemetry/instrumentation-http` redacts sensitive URL query parameters on outgoing (client) spans but not on incoming (server) spans. The server-span path writes the raw query string verbatim into the `url.query` attribute, so credentials embedded in inbound request URLs — AWS presigned-URL signatures, Azure SAS tokens (`sig`), GCS signed-URL signatures — are exported in plaintext to the configured tracing backend. Configuring the `redactedQueryParams` option does not change this, as this applies only to outgoing (client) spans.

Impact Information disclosure / credential leakage (CWE-200; CWE-532, insertion of sensitive information into telemetry data). Who is impacted: any Node.js service instrumented with `@opentelemetry/instrumentation-http` — directly or transitively via `@opentelemetry/auto-instrumentations-node` — that receives inbound requests carrying credentials in the query string. Common cases: services fronting presigned S3/GCS…

Published by the source

13 Nov 2026, 19:29 UTC

Last modified by the source

13 Nov 2026, 19:45 UTC

Source last checked

14 Nov 2026, 07:30 UTC

1. Revision 2 · amended · 14 Nov 2026

   Amended from osv record GHSA-3v2p-hm54-8qcq

2. Revision 1 · created · 13 Nov 2026

   Published from ghsa record GHSA-3v2p-hm54-8qcq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-128080

Advisory: OpenTelemetry JavaScript: Insertion of Sensitive Information into Log File and Exposure of Sensitive Information to an Unauthorized Actor in @opentelemetry/instrumentation-http
IDs: CVE-2026-128080, GHSA-3v2p-hm54-8qcq
Record: https://patchnext.com/advisories/cve-2026-128080 (revision 2, source checked 14 Nov 2026, 07:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @opentelemetry/instrumentation-http 0.222.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @opentelemetry/instrumentation-http: affected >= 0.204.0, < 0.222.0; fixed in 0.222.0

## Suggested inspection (read-only)
- `npm ls @opentelemetry/instrumentation-http --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @opentelemetry/instrumentation-http.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3v2p-hm54-8qcq (GitHub-reviewed advisory GHSA-3v2p-hm54-8qcq lists affected ranges: npm @opentelemetry/instrumentation-http >=0.204.0 <0.222.0)
- Verified: https://osv.dev/vulnerability/GHSA-3v2p-hm54-8qcq (OSV record GHSA-3v2p-hm54-8qcq lists affected ranges: npm @opentelemetry/instrumentation-http >=0.204.0 <0.222.0 (fixed))

Commands are suggestions: review each one before running it.