CVE-2026-50276

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” 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.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

dd-trace-rb is Datadog's client library for Ruby. Prior to 2.32.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 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 2.32.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG 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 25, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

2.32.0

Patch available: DataDog/dd-trace-rb v2.32.0

https://github.com/DataDog/dd-trace-rb/releases/tag/v2.32.0
GitHub commit Patch Available

commit 361947090214 (DataDog/dd-trace-rb)

Patch available: DataDog/dd-trace-rb v2.32.0 (contains commit 361947090214)

https://github.com/DataDog/dd-trace-rb/commit/361947090214488778ac4f144e219426ffcf92e6
GitHub pull request Patch Available

Limit processing of large Baggage data

Patch available: DataDog/dd-trace-rb v2.32.0 (PR #5672 merged 2026-05-06)

https://github.com/DataDog/dd-trace-rb/pull/5672
GitHub advisoryMentions a patch (unverified)

Improper parsing of W3C baggage headers may lead to DoS · Advisory · DataDog/dd-trace-rb · GitHub

https://github.com/DataDog/dd-trace-rb/security/advisories/GHSA-p5f6-rccc-jv98

Vendor Advisories for CVE-2026-50276(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)
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
datadog2.0.0 ... 2.9.0 (38 versions)
  • every version up to 2.32.0: fixed in 2.32.0
—

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.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  3. 2026-10-12 15:59 UTCEG score recompute
  4. 2026-10-11 19:42 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  18. 2026-10-01 12:35 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  21. 2026-09-28 08:40 UTCEG score recompute
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  23. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  24. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  25. 2026-09-25 14:25 UTCEG score recompute
Show 14 more
  1. 2026-09-24 08:45 UTCEG score recompute
  2. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  3. 2026-09-23 03:12 UTCEG score recompute
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  6. 2026-09-18 04:42 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  9. 2026-09-14 18:38 UTCEG score recompute
  10. 2026-09-14 18:08 UTCEG score recompute
  11. 2026-07-30 21:40 UTCEG score recompute
  12. 2026-07-26 11:28 UTCEG score recompute
  13. 2026-07-23 03:18 UTCEG score recompute
  14. 2026-07-15 23:19 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-50276?
CVE-2026-50276 is a high-severity vulnerability; its CVE record was published on July 15, 2026. dd-trace-rb is Datadog's client library for Ruby. Prior to 2.32.0, W3C baggage extraction does not enforce DDTRACEBAGGAGEMAXITEMS, which defaults to 64, or DDTRACEBAGGAGEMAXBYTES, which defaults to 8192, although those limits apply during baggage injection. A remote unauthenticated attacker can…
When was the CVE record for CVE-2026-50276 published?
The CVE record for CVE-2026-50276 was published on July 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 25, 2026; the record at its source may have been updated since.
Is CVE-2026-50276 actively exploited?
CVE-2026-50276 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50276?
CVE-2026-50276 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50276?
A fix for CVE-2026-50276 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50276 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50276

Explore →

Is Your Infrastructure Affected by CVE-2026-50276?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.