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.
CVE-2026-50270
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (55th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%The EG Score, 7.5 of 10.Exploitation0.8% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.8%
- EPSS %ILE
- 55th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
July 15, 2026
Last Modified
September 30, 2026
Advisory Details (4)
Auto-updated Sep 14, 20261.62.0
Patch available: DataDog/dd-trace-java v1.62.0
https://github.com/DataDog/dd-trace-java/releases/tag/v1.62.0commit 16c6a5fd1fed (DataDog/dd-trace-java)
Fix landed in DataDog/dd-trace-java commit 16c6a5fd1fed — awaiting tagged release
https://github.com/DataDog/dd-trace-java/commit/16c6a5fd1fed71cef6c35f69122f19f5ee242757Add items and bytes limits to baggage extraction
Fix merged in DataDog/dd-trace-java PR #11265 on 2026-05-04 — awaiting tagged release
https://github.com/DataDog/dd-trace-java/pull/11265Improper parsing of W3C baggage headers may lead to DoS · Advisory · DataDog/dd-trace-java · GitHub
https://github.com/DataDog/dd-trace-java/security/advisories/GHSA-74xj-wh4w-vqxcVendor Advisories for CVE-2026-50270(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| com.datadoghq:dd-java-agent | 0.0.1 ... 1.9.0 (291 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 35× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
- 2026-10-12 15:59 UTCEG score recompute
- 2026-10-11 19:42 UTCEG score recompute
- 2026-10-11 16:57 UTCEG score recompute
- 2026-10-11 14:21 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 55th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 55th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 55th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.8% · 55th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-09-30 17:52 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-09-28 08:40 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-09-24 08:45 UTCEG score recompute
Show 14 moreShow fewer
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-23 03:13 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-18 04:42 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-14 20:27 UTCEG score recompute
- 2026-09-14 19:30 UTCEG score recompute
- 2026-09-14 18:38 UTCEG score recompute
- 2026-07-30 10:41 UTCEG score recompute
- 2026-07-26 11:28 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-15 22:54 UTCEG score recompute
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-50270?
When was the CVE record for CVE-2026-50270 published?
Is CVE-2026-50270 actively exploited?
What is the CVSS score of CVE-2026-50270?
How do I remediate CVE-2026-50270?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50270
Is Your Infrastructure Affected by CVE-2026-50270?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.