Quick answers
- Is CVE-2026-50271 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50271 being exploited in the wild.
- How severe is CVE-2026-50271?
- High severity, with a CVSS score of 7.5, published 17 July 2026.
- Which products and versions are affected?
- Datadog Dd-Trace-Py < 4.8.2; ddtrace (PyPI) < 4.8.2, ECOSYSTEM:introduced=0,fixed=4.8.2.
- Is there a fix for CVE-2026-50271?
- Yes. ddtrace (PyPI): upgrade to 4.8.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-50271 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-50271?
- Check whether you run Datadog Dd-Trace-Py or ddtrace (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ddtrace (PyPI): upgrade to 4.8.2 or later
pip install "ddtrace>=4.8.2"
Technical details
A resource exhaustion vulnerability (CWE-770) exists in the Datadog Python APM client (dd-trace-py) during the extraction of W3C baggage headers. While limits like DD_TRACE_BAGGAGE_MAX_ITEMS and DD_TRACE_BAGGAGE_MAX_BYTES were enforced during header injection, they were ignored during extraction. An unauthenticated remote attacker can exploit this by sending HTTP requests with excessively large baggage headers or a high volume of key-value pairs. This causes the tracer to perform unbounded memory allocation and CPU-intensive parsing, leading to a Denial of Service (DoS). The vulnerability is present in the default configuration where baggage propagation is enabled. It is fixed in version 4.8.2.
Affected products
- Datadog dd-trace-py < 4.8.2
Identifiers
- CVE-2026-50271
- GHSA-mw54-j2v2-42hr
- PYSEC-2026-3461
Timeline
- 2026-05-06: patched: Fix merged into 4.8 branch and released in v4.8.2
- 2026-06-05: advisory: GitHub Security Advisory GHSA-mw54-j2v2-42hr published
- 2026-07-17: disclosed: CVE-2026-50271 published to NVD