CVE Catalog

CVE-2026-50270

HighCVSS 7.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Elevated risk
0.79%

55th percentile - higher than 55% of all known CVEs

Summary

In dd-trace-java before 1.62.0, W3C baggage extraction does not enforce DD_TRACE_BAGGAGE_MAX_ITEMS (default 64) or DD_TRACE_BAGGAGE_MAX_BYTES (default 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, causing unbounded CPU and memory consumption.

Risk Assessment

Can cause denial of service in an HTTP service where the baggage propagation style is enabled (the default for most affected tracers). Every request allocates map entries while parsing the attacker-controlled header.

Recommendation

Update dd-trace-java to version 1.62.0 (or later). Consider enforcing header size limits at the HTTP server level.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS