Vulnerability in dd-trace (CVE-2026-50272)
Summary
Vulnerability in dd-trace (CVE-2026-50272). Risk of unauthorized operations or information disclosure. Exploitable via baggage. Mitigation: upgrade to 5.100.0 or later.
Original description
The description as published by the source.
dd-trace is the Datadog APM client for Node.js. Prior to 5.100.0, W3C baggage propagation in packages/dd-trace/src/baggage.js and packages/dd-trace/src/opentracing/propagation/text_map.js parsed incoming baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES on extraction. A remote, unauthenticated attacker can send a request whose baggage header contains an arbitrarily large number of comma-separated key-value pairs, or a single very large value, causing unbounded CPU and memory consumption and enabling a remote denial of service against any HTTP service with baggage propagation enabled. This issue is fixed in version 5.100.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50272 has been found in dd-trace.
Attackers can target a specific entry point like baggage over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade dd-trace to 5.100.0 or later.
If unsure, ask your IT team or search "dd-trace CVE-2026-50272" on the vendor's site.
CVE-2026-50272 (dd-trace) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: baggage / DD_TRACE_PROPAGATION_STYLE / DD_TRACE_PROPAGATION_STYLE_EXTRACT / LimitRequestFieldSize
Patched: 5.100.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-770) exists in dd-trace. Attackers reach the vulnerable code path via baggage without authentication.
Check the vendor advisory for the affected versions of dd-trace. Attack surface: baggage / DD_TRACE_PROPAGATION_STYLE / DD_TRACE_PROPAGATION_STYLE_EXTRACT / LimitRequestFieldSize.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 5.100.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'dd-trace' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dd-trace' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dd-traceを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade dd-trace to 5.100.0ステージング環境で 5.100.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com
- web github.com