Skip to main content
VulnerabilityPublished

CVE-2026-50271: dd-trace-py · Improper parsing of W3C baggage headers may lead to DoS

Affects ddtraceSource GCVE Database

0

Not known to be exploited · CVSS 7.5 High : upgrade to 4.8.2 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.8.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade ddtrace to 4.8.2.

Affected software

ProductAffectedFixed in
PyPIddtraceAffected
  • <4.8.2
Fixed in
  • 4.8.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in dd-trace-py version 4.8.2. Users should upgrade to version 4.8.2 or later to address this vulnerability. No other mitigation or temporary workaround is indicated in the provided data.

Description

The dd-trace-py library versions prior to 4.8.2 contain a vulnerability in the parsing of W3C baggage HTTP headers. The library does not enforce limits on the number or size of baggage items during extraction, allowing remote unauthenticated attackers to send requests with excessively large or numerous baggage items. This can cause unbounded CPU and memory consumption, resulting in a remote denial of service (DoS) against HTTP services using the affected tracer with baggage propagation enabled by default.

References

Community reviews

Loading reviews…