CVE-2026-50275

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.7% (53rd 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

Also known asEUVD-2026-82416 (ENISA EUVD)Source: ENISA EUVD

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.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The Datadog PHP Tracer provides application performance monitoring and distributed tracing for PHP. Prior to 1.19.2, ddtrace_deserialize_baggage in ext/distributed_tracing_headers.c parses incoming W3C baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES. A remote unauthenticated client can send an arbitrarily large number of comma-separated key-value pairs or a single oversized value, causing the tracer to allocate hash-map entries and consume unbounded CPU and memory on each request. Baggage extraction is enabled by default in most affected deployments unless baggage is removed from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT. This issue is fixed in version 1.19.2.

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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

September 17, 2026

Last Modified

September 23, 2026

Advisory Details (6)

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

1.20.0

Patch available: DataDog/dd-trace-php 1.20.0

https://github.com/DataDog/dd-trace-php/releases/tag/1.20.0
GitHub release Patch Available

1.19.2

Patch available: DataDog/dd-trace-php 1.19.2

https://github.com/DataDog/dd-trace-php/releases/tag/1.19.2
GitHub commit

commit 43072ccafe55 (DataDog/dd-trace-php)

Fix landed in DataDog/dd-trace-php commit 43072ccafe55 — awaiting tagged release

https://github.com/DataDog/dd-trace-php/commit/43072ccafe55a5dbdfba75a42bf316b4150ae1e5
GitHub commit

commit 2f7987eb02e3 (DataDog/dd-trace-php)

Fix landed in DataDog/dd-trace-php commit 2f7987eb02e3 — awaiting tagged release

https://github.com/DataDog/dd-trace-php/commit/2f7987eb02e306bb62bce8ec4152dece68112f51
GitHub pull request

Restrict the accepted amount of extracted tags and baggage

Fix merged in DataDog/dd-trace-php PR #3854 on 2026-05-06 — awaiting tagged release

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

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

https://github.com/DataDog/dd-trace-php/security/advisories/GHSA-phwx-ww2p-cv9v

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-12 19:23 UTCEchelonGraph re-scored
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-11-06 05:28 UTCEchelonGraph re-scored
  11. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-30 15:35 UTCEchelonGraph re-scored
  19. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-25 14:22 UTCEchelonGraph re-scored
  25. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 66 more
  1. 2026-10-24 01:41 UTCEchelonGraph re-scored
  2. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  7. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-18 03:33 UTCEchelonGraph re-scored
  9. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-17 11:47 UTCEchelonGraph re-scored
  11. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-12 15:59 UTCEchelonGraph re-scored
  17. 2026-10-11 19:42 UTCEchelonGraph re-scored
  18. 2026-10-11 16:57 UTCEchelonGraph re-scored
  19. 2026-10-11 14:21 UTCEchelonGraph re-scored
  20. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-10-10 23:03 UTCEchelonGraph re-scored
  22. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-10 00:38 UTCEchelonGraph re-scored
  24. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-08 23:17 UTCEchelonGraph re-scored
  26. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-08 00:27 UTCEchelonGraph re-scored
  28. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-10-07 02:02 UTCEchelonGraph re-scored
  30. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-10-06 03:17 UTCEchelonGraph re-scored
  32. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-10-05 04:26 UTCEchelonGraph re-scored
  34. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-10-03 18:49 UTCEchelonGraph re-scored
  36. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  37. 2026-10-02 20:11 UTCEchelonGraph re-scored
  38. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  39. 2026-10-01 21:40 UTCEchelonGraph re-scored
  40. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-09-30 23:12 UTCEchelonGraph re-scored
  42. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-09-30 00:42 UTCEchelonGraph re-scored
  44. 2026-09-28 22:14 UTCEchelonGraph re-scored
  45. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  46. 2026-09-27 23:43 UTCEchelonGraph re-scored
  47. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  48. 2026-09-27 01:19 UTCEchelonGraph re-scored
  49. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  50. 2026-09-26 02:28 UTCEchelonGraph re-scored
  51. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  52. 2026-09-24 16:52 UTCEchelonGraph re-scored
  53. 2026-09-23 18:28 UTCEchelonGraph re-scored
  54. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  55. 2026-09-23 01:23 UTCEchelonGraph re-scored
  56. 2026-09-22 02:59 UTCEchelonGraph re-scored
  57. 2026-09-21 04:36 UTCEchelonGraph re-scored
  58. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  59. 2026-09-19 18:57 UTCEchelonGraph re-scored
  60. 2026-09-18 20:34 UTCEchelonGraph re-scored
  61. 2026-09-18 20:10 UTCEchelonGraph re-scored
  62. 2026-09-18 19:44 UTCEchelonGraph re-scored
  63. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  64. 2026-09-17 21:20 UTCEchelonGraph re-scored
  65. 2026-09-17 20:25 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  66. 2026-09-17 20:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-50275?
CVE-2026-50275 is a high-severity vulnerability; its CVE record was published on September 17, 2026. The Datadog PHP Tracer provides application performance monitoring and distributed tracing for PHP. Prior to 1.19.2, ddtrace_deserialize_baggage in ext/distributed_tracing_headers.c parses incoming W3C baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES.…
When was the CVE record for CVE-2026-50275 published?
The CVE record for CVE-2026-50275 was published on September 17, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-50275 actively exploited?
CVE-2026-50275 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50275?
CVE-2026-50275 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-50275?
A fix for CVE-2026-50275 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50275

Explore →

Is Your Infrastructure Affected by CVE-2026-50275?

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