CVE-2026-50273

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.

Datadog .NET Tracer is a client library for Datadog APM for .NET applications. Prior to 3.43.0, Datadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES on extraction, allowing a remote unauthenticated attacker to send a baggage header with many comma-separated key-value pairs or one very large value and cause unbounded CPU and memory consumption in services with baggage propagation enabled. This issue is fixed in version 3.43.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

July 17, 2026

Advisory Details (4)

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

3.43.0

Patch available: DataDog/dd-trace-dotnet v3.43.0

https://github.com/DataDog/dd-trace-dotnet/releases/tag/v3.43.0
GitHub commit

commit 38092e0d41a3 (DataDog/dd-trace-dotnet)

Fix landed in DataDog/dd-trace-dotnet commit 38092e0d41a3 — awaiting tagged release

https://github.com/DataDog/dd-trace-dotnet/commit/38092e0d41a36decbe649e048e48ae1b1607292f
GitHub pull request

Apply baggage limits on extract

Fix merged in DataDog/dd-trace-dotnet PR #8555 on 2026-05-04 — awaiting tagged release

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

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

https://github.com/DataDog/dd-trace-dotnet/security/advisories/GHSA-38wr-vpc7-2mp4

Vendor Advisories for CVE-2026-50273(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
NuGet(2)
PackageVulnerable rangeFix by version rangeDependents
Datadog.Trace0.1.0 ... 3.9.1 (230 versions)
  • every version up to 3.43.0: fixed in 3.43.0
—
Datadog.Trace.OpenTracing0.2.3-alpha ... 3.9.1 (221 versions)
  • every version up to 3.43.0: fixed in 3.43.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 32× 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.

Showing the most recent 100 of 125 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 25 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  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-24 08:45 UTCEG score recompute
Show 75 more
  1. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  2. 2026-09-23 03:13 UTCEG score recompute
  3. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  4. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  5. 2026-09-18 04:42 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  7. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-09-13 23:10 UTCEG score recompute
  9. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-09-13 07:11 UTCEG score recompute
  11. 2026-09-11 21:43 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  13. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  14. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  15. 2026-09-08 00:40 UTCEG score recompute
  16. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  17. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  18. 2026-09-05 20:45 UTCEG score recompute
  19. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  20. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  21. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  22. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  23. 2026-08-31 03:47 UTCEG score recompute
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  25. 2026-08-30 03:43 UTCEG score recompute
  26. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  27. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  28. 2026-08-28 01:51 UTCEG score recompute
  29. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  30. 2026-08-26 23:44 UTCEG score recompute
  31. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  32. 2026-08-25 23:53 UTCEG score recompute
  33. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  34. 2026-08-24 22:02 UTCEG score recompute
  35. 2026-08-24 10:16 UTCEG score recompute
  36. 2026-08-23 10:46 UTCEG score recompute
  37. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-08-22 11:17 UTCEG score recompute
  39. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  40. 2026-08-21 00:01 UTCEG score recompute
  41. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  42. 2026-08-20 00:06 UTCEG score recompute
  43. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-08-18 19:57 UTCEG score recompute
  45. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  46. 2026-08-18 02:31 UTCEG score recompute
  47. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  48. 2026-08-17 02:00 UTCEG score recompute
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  50. 2026-08-16 02:30 UTCEG score recompute
  51. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  52. 2026-08-15 03:01 UTCEG score recompute
  53. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  54. 2026-08-14 03:32 UTCEG score recompute
  55. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  56. 2026-08-12 16:18 UTCEG score recompute
  57. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  58. 2026-08-11 16:37 UTCEG score recompute
  59. 2026-08-11 04:51 UTCEG score recompute
  60. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  61. 2026-08-09 17:37 UTCEG score recompute
  62. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  63. 2026-08-08 18:09 UTCEG score recompute
  64. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  65. 2026-08-07 18:39 UTCEG score recompute
  66. 2026-08-06 19:06 UTCEG score recompute
  67. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  68. 2026-08-05 19:37 UTCEG score recompute
  69. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  70. 2026-08-04 20:05 UTCEG score recompute
  71. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  72. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  73. 2026-08-03 20:35 UTCEG score recompute
  74. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  75. 2026-08-02 09:21 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50273?
CVE-2026-50273 is a high-severity vulnerability; its CVE record was published on July 15, 2026. Datadog .NET Tracer is a client library for Datadog APM for .NET applications. Prior to 3.43.0, Datadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing DDTRACEBAGGAGEMAXITEMS or DDTRACEBAGGAGEMAXBYTES on extraction, allowing a remote…
When was the CVE record for CVE-2026-50273 published?
The CVE record for CVE-2026-50273 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 July 17, 2026; the record at its source may have been updated since.
Is CVE-2026-50273 actively exploited?
CVE-2026-50273 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-50273?
CVE-2026-50273 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-50273?
A fix for CVE-2026-50273 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50273 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-50273

Explore →

Is Your Infrastructure Affected by CVE-2026-50273?

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

Book a Demo →Browse All CVEs