CVE-2026-50277

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

dd-trace-cpp is the Datadog distributed tracing library for C++. Prior to 2.1.0, dd-trace-cpp parses incoming W3C baggage headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES on the extraction path, even though those limits are enforced during injection. A remote unauthenticated attacker can send a header containing many comma-separated key-value pairs or one very large value, causing per-request hash-map allocation and unbounded CPU and memory consumption. Baggage extraction is enabled by default in most affected tracers unless baggage is removed from DD_TRACE_PROPAGATION_STYLE or DD_TRACE_PROPAGATION_STYLE_EXTRACT, so affected internet-facing services can be denied service. This issue is fixed in version 2.1.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (4)

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

v2.1.0

Patch available: DataDog/dd-trace-cpp v2.1.0

https://github.com/DataDog/dd-trace-cpp/releases/tag/v2.1.0
github_commit Patch Available

commit 422dc91bb93e (DataDog/dd-trace-cpp)

Patch available: DataDog/dd-trace-cpp v2.1.0 (contains commit 422dc91bb93e)

https://github.com/DataDog/dd-trace-cpp/commit/422dc91bb93e358e3977381275d311f3f926d666
github_pr Patch Available

fix: observe baggage limits on extraction

Patch available: DataDog/dd-trace-cpp v2.1.0 (PR #313 merged 2026-05-04)

https://github.com/DataDog/dd-trace-cpp/pull/313
github Patch Available

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

https://github.com/DataDog/dd-trace-cpp/security/advisories/GHSA-ch7h-phmx-rqwq

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 18:51 UTCEG score recompute
  3. 2026-09-18 20:06 UTCEG score recompute
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-17 21:20 UTCEG score recompute
  6. 2026-09-17 20:25 UTCEG score recompute
  7. 2026-09-17 20:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50277?
CVE-2026-50277 is a high vulnerability published on September 17, 2026. dd-trace-cpp is the Datadog distributed tracing library for C++. Prior to 2.1.0, dd-trace-cpp parses incoming W3C baggage headers without enforcing DDTRACEBAGGAGEMAXITEMS or DDTRACEBAGGAGEMAXBYTES on the extraction path, even though those limits are enforced during injection. A remote…
When was CVE-2026-50277 disclosed?
CVE-2026-50277 was first published in the National Vulnerability Database on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50277 actively exploited?
CVE-2026-50277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.5% of all scored CVEs.
What is the CVSS score of CVE-2026-50277?
CVE-2026-50277 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-50277?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50277, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50277?

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

Start Free Scan →Browse All CVEs