{"id":"GHSA-3v2p-hm54-8qcq","summary":"OpenTelemetry JavaScript: Insertion of Sensitive Information into Log File and Exposure of Sensitive Information to an Unauthorized Actor in @opentelemetry/instrumentation-http","details":"### Summary\n\n`@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.\n\nConfiguring the `redactedQueryParams` option **does not change this**, as this applies only to outgoing (client) spans.\n\n### Impact\n\n**Information disclosure / credential leakage** (CWE-200; CWE-532, insertion of sensitive information into telemetry data).\n\n**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 downloads, Azure SAS-token URLs, and signature-authenticated webhooks.\n\n**Consequence:** clients' still-valid credentials are written into server spans and stored by the tracing backend, readable by anyone with span-read access — observability vendor infrastructure, dashboard users, and internal audiences far broader than the credential's intended scope. Presigned-URL signatures typically remain valid for minutes to days after capture, so this is not merely historical exposure.\n\n**Severity:** Moderate. Exploitation requires read access to the telemetry backend, and inbound URLs must actually carry signed credentials. However, the gap is a documented mitigation that silently fails to apply, which defeats the mitigation operators would reach for.\n\n### Patches\n\nThis vulnerability has been patched in `@opentelemetry/instrumentation-http` version `0.222.0`.\nKnown sensitive query string values (as defined by Semantic Conventions) are redacted by default from span data for incoming spans.\nThe `redactedQueryParamsServer` configuration option was added for customization.","aliases":["CVE-2026-128080"],"modified":"2026-11-13T19:45:03.811898272Z","published":"2026-11-13T19:29:20Z","database_specific":{"severity":"MODERATE","github_reviewed":true,"github_reviewed_at":"2026-11-13T19:29:20Z","nvd_published_at":null,"cwe_ids":["CWE-200","CWE-532"]},"references":[{"type":"WEB","url":"https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-3v2p-hm54-8qcq"},{"type":"WEB","url":"https://github.com/open-telemetry/opentelemetry-js/commit/e086dec7f9304107ef6d50b5877be88895c06aa7"},{"type":"PACKAGE","url":"https://github.com/open-telemetry/opentelemetry-js"},{"type":"WEB","url":"https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental/v0.222.0"}],"affected":[{"package":{"name":"@opentelemetry/instrumentation-http","ecosystem":"npm","purl":"pkg:npm/%40opentelemetry/instrumentation-http"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0.204.0"},{"fixed":"0.222.0"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-3v2p-hm54-8qcq/GHSA-3v2p-hm54-8qcq.json"}}],"schema_version":"1.9.2","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N"}]}