← Back
CVE-2026-50272
high
CVSS 7.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-770) exists in dd-trace. Attackers reach the vulnerable code path via ``baggage`` without authentication.
📍 Affected scope
dd-trace — . Attack surface: `baggage` / `DD_TRACE_PROPAGATION_STYLE` / `DD_TRACE_PROPAGATION_STYLE_EXTRACT` / `LimitRequestFieldSize`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.100.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade dd-trace to 5.100.0ステージング環境で 5.100.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
dd-trace
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.100.0"}]}]