dd-trace-java: Improper parsing of W3C baggage headers may lead to DoS (CVE-2026-50270) | HOL Guard CVE

High severityCVE-2026-50270GHSA-74XJ-WH4W-VQXC

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

Answer in brief

CVE-2026-50270 records a High severity vulnerability in dd-trace-java: Improper parsing of W3C baggage headers may lead to DoS. The current sources do not mark it as known exploited. The current feed maps com.datadoghq/dd-java-agent (generic), DataDog/dd-trace-java (generic), com.datadoghq:dd-java-agent (maven). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 14, 2026Updated Sep 14, 2026Source checked Sep 17, 2026First seen by HOL Jul 15, 2026Material review Sep 14, 2026

Upstream Advisory

Key facts

Risk: High
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps com.datadoghq/dd-java-agent (generic), DataDog/dd-trace-java (generic), com.datadoghq:dd-java-agent (maven). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
com.datadoghq/dd-java-agentgeneric	< 1.62.0	Not reported
DataDog/dd-trace-javageneric	< 1.62.0	Not reported
com.datadoghq:dd-java-agentmaven	<1.62.0	1.62.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for com.datadoghq/dd-java-agent, DataDog/dd-trace-java, com.datadoghq:dd-java-agent.
Review the reported fix. Update com.datadoghq:dd-java-agent to 1.62.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 15, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.