What’s Vulnerable › Vulnerabilities

CVE-2026-50270: dd-trace-java: Improper parsing of W3C baggage headers may lead to DoS

• Severity: high (CVSS 7.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.8% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-09-14 · updated 2026-09-30
• Weakness: CWE-770

Description

dd-trace-java is a Datadog APM client for Java. Prior to 1.62.0, W3C baggage extraction does not enforce DD_TRACE_BAGGAGE_MAX_ITEMS, which defaults to 64, or DD_TRACE_BAGGAGE_MAX_BYTES, which defaults to 8192, although those limits apply during baggage injection. A remote unauthenticated attacker can send a baggage HTTP header containing many comma-separated key-value pairs or a single very large value. The extraction path allocates map entries while parsing the attacker-controlled header on every request, causing unbounded CPU and memory consumption in an HTTP service where the baggage propagation style is enabled, which is the default for most affected tracers. This can cause denial of service. This issue is fixed in version 1.62.0.

Affected products

• com.datadoghq dd-java-agent: before 1.62.0
• DataDog dd-trace-java: before 1.62.0

References

• https://github.com/DataDog/dd-trace-java/commit/16c6a5fd1fed71cef6c35f69122f19f5ee242757
• https://github.com/DataDog/dd-trace-java/pull/11265
• https://github.com/DataDog/dd-trace-java/releases/tag/v1.62.0
• https://github.com/DataDog/dd-trace-java/security/advisories/GHSA-74xj-wh4w-vqxc

Get alerted when CVE-2026-50270 or the next vulnerability affects your stack