Skip to content

fix(deps): update dependency @opentelemetry/instrumentation-http to ^0.301.0 [security] - #3048

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-opentelemetry-instrumentation-http-vulnerability
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-opentelemetry-instrumentation-http-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@opentelemetry/instrumentation-http (source) ^0.219.0 → ^0.301.0 age confidence

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

CVE-2026-128080 / GHSA-3v2p-hm54-8qcq

More information

Details

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.

Severity

  • CVSS Score: 5.8 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

open-telemetry/opentelemetry-js (@​opentelemetry/instrumentation-http)

v0.301.2

Compare Source

v0.301.1

Compare Source

v0.301.0

Compare Source

v0.300.0

Compare Source

v0.223.2

Compare Source

v0.223.1

Compare Source

v0.223.0

Compare Source

v0.222.0

Compare Source

v0.221.0

Compare Source

v0.220.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added area: dependencies Pull requests that update a dependency file dependencies Pull requests that update a dependency file status: ready Ready for review labels Nov 14, 2026
@vercel

vercel Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
cloud Skipped Skipped Nov 14, 2026 2:01am UTC
showcase Skipped Skipped Nov 14, 2026 2:01am UTC
tambo-docs Skipped Skipped Nov 14, 2026 2:01am UTC

Request Review

@renovate
renovate Bot enabled auto-merge (squash) November 14, 2026 02:01
@vercel
vercel Bot temporarily deployed to Preview – cloud November 14, 2026 02:01 Inactive
@vercel
vercel Bot temporarily deployed to Preview – tambo-docs November 14, 2026 02:01 Inactive
@vercel
vercel Bot temporarily deployed to Preview – showcase November 14, 2026 02:01 Inactive
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​opentelemetry/​instrumentation-http@​0.219.0 ⏵ 0.301.2100 +24100 +210099 +4100

View full report

@codecov

codecov Bot commented Nov 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

This branch was previously deployed

3 inactive deployments
Preview – cloud — 0362a70a Deployed Nov 14, 2026 by vercel[bot]
Preview – tambo-docs — 0362a70a Deployed Nov 14, 2026 by vercel[bot]
Preview – showcase — 0362a70a Deployed Nov 14, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: dependencies Pull requests that update a dependency file dependencies Pull requests that update a dependency file status: ready Ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants