Medium

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

  • Disclosed: 13.11.2026
  • Updated: 13.11.2026 21:17

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 downloads, Azure SAS-token URLs, and signature-authenticated webhooks.

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.

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.

Patches

This vulnerability has been patched in @opentelemetry/instrumentation-http version 0.222.0. Known sensitive query string values (as defined by Semantic Conventions) are redacted by default from span data for incoming spans. The redactedQueryParamsServer configuration option was added for customization.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package @opentelemetry/instrumentation-http >= 0.204.0, < 0.222.0 0.222.0

References

CVSS score 5.8/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Weakness (CWE)
CWE-200, CWE-532
Platform
npm
Package
@opentelemetry/instrumentation-http
Disclosed
13.11.2026
Updated
13.11.2026 21:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-3v2p-hm54-8qcq - CC BY 4.0

Vulnerability history: @opentelemetry/instrumentation-http

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

This is the only known vulnerability of this package.

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.