Service interruption via unbounded baggage extraction
Published Sep 14, 2026 · Updated Sep 14, 2026
Resource exhaustion in Datadog dd-trace-java before 1.62.0 allows remote attackers to interrupt HTTP services via baggage headers. The W3C baggage extraction path parses attacker-controlled header values into hash-map entries without enforcing the configured item-count or byte-size limits. Exposure requires an instrumented HTTP service with baggage extraction enabled; repeated oversized headers consume unbounded CPU and memory until the service becomes unavailable.
Summary
What happened
Resource exhaustion in Datadog dd-trace-java before 1.62.0 allows remote attackers to interrupt HTTP services via baggage headers. The W3C baggage extraction path parses attacker-controlled header values into hash-map entries without enforcing the configured item-count or byte-size limits. Exposure requires an instrumented HTTP service with baggage extraction enabled; repeated oversized headers consume unbounded CPU and memory until the service becomes unavailable.
The record
- CVE
- CVE-2026-50270
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Datadog
- Product
- Datadog Java Agent
- Classifications
- CWE-770, CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.62.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo