CVE-2026-116588

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th 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
Trending — 3 sources updated this week

Also known asEUVD-2026-110469 (ENISA EUVD) · GHSA-3633-r77q-h3v3 (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

Datadog dd-trace-py is the Datadog Python APM client. From 1.5.0 until 3.19.9 and 4.15.6, the default query-string obfuscation regular expression can exhibit excessive backtracking while synchronously processing attacker-controlled URL query strings for HTTP span metadata. A remote attacker can cause prolonged CPU consumption, request latency, and service unavailability in affected HTTP tracing integrations that include query strings in URL span tags. The vulnerable processing is enabled by default for those integrations. This issue is fixed in versions 3.19.9 and 4.15.6.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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.5%
EPSS %ILE
40th
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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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

October 26, 2026

Last Modified

November 2, 2026

Advisory Details (9)

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

4.15.6

Patch available: DataDog/dd-trace-py v4.15.6

https://github.com/DataDog/dd-trace-py/releases/tag/v4.15.6
GitHub release Patch Available

3.19.9

Patch available: DataDog/dd-trace-py v3.19.9

https://github.com/DataDog/dd-trace-py/releases/tag/v3.19.9
GitHub commit Patch Available

commit a6d73607ea45 (DataDog/dd-trace-py)

Patch available: DataDog/dd-trace-py v4.16.0rc1 (contains commit a6d73607ea45)

https://github.com/DataDog/dd-trace-py/commit/a6d73607ea45ecd67152630f64b0945556972ed8
GitHub commit Patch Available

commit 83ea39845dd9 (DataDog/dd-trace-py)

Patch available: DataDog/dd-trace-py v4.15.6 (contains commit 83ea39845dd9)

https://github.com/DataDog/dd-trace-py/commit/83ea39845dd95bfb9b8e247c62b3d22fc5dce1ce
GitHub commit Patch Available

commit 63ddc3cb07d8 (DataDog/dd-trace-py)

Patch available: DataDog/dd-trace-py v3.19.9 (contains commit 63ddc3cb07d8)

https://github.com/DataDog/dd-trace-py/commit/63ddc3cb07d8813ded7a8b3ab5b8d0f5470e4bfd
GitHub pull request Patch Available

fix(tracing): prevent quadratic query string obfuscation [backport 3.19]

Patch available: DataDog/dd-trace-py v3.19.9 (PR #20880 merged 2026-10-09)

https://github.com/DataDog/dd-trace-py/pull/20880
GitHub pull request Patch Available

fix(tracing): prevent quadratic query string obfuscation [backport 4.15]

Patch available: DataDog/dd-trace-py v4.15.6 (PR #20862 merged 2026-10-07)

https://github.com/DataDog/dd-trace-py/pull/20862
GitHub pull request Patch Available

fix(tracing): prevent quadratic query string obfuscation

Patch available: DataDog/dd-trace-py v4.16.0rc1 (PR #20857 merged 2026-10-07)

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

ReDOS in URL query string obfuscation · Advisory · DataDog/dd-trace-py · GitHub

https://github.com/DataDog/dd-trace-py/security/advisories/GHSA-3633-r77q-h3v3

Vendor Advisories for CVE-2026-116588(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipddtrace @ 3.19.9 (fixes >= 1.5.0, < 3.19.9)—ghsa
pipddtrace @ 4.15.6 (fixes >= 4.0.0, < 4.15.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
ddtrace1.10.0 ... 3.9.4 (464 versions)
  • 1.5.0 up to 3.19.9: fixed in 3.19.9
  • 4.0.0 up to 4.15.6: fixed in 4.15.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 17× 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-11-02 19:27 UTCEG score recompute
  2. 2026-11-02 19:27 UTCGHSA enrichmentGHSA-3633-r77q-h3v3 · GitHub severity HIGH
  3. 2026-11-02 18:23 UTCEG score recompute
  4. 2026-11-02 18:23 UTCGHSA enrichmentGHSA-3633-r77q-h3v3 · GitHub severity HIGH
  5. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-3633-r77q-h3v3 · GitHub severity HIGH
  8. 2026-11-01 07:59 UTCEG score recompute
  9. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-26 22:39 UTCEG score recompute
  15. 2026-10-26 22:01 UTCENISA EUVD ID recordedEUVD-2026-110469 · Source: ENISA EUVD
  16. 2026-10-26 21:36 UTCEG score recomputeFirst assessed: 8.7 HIGH
  17. 2026-10-26 21:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-116588?
CVE-2026-116588 is a high-severity vulnerability; its CVE record was published on October 26, 2026. Datadog dd-trace-py is the Datadog Python APM client. From 1.5.0 until 3.19.9 and 4.15.6, the default query-string obfuscation regular expression can exhibit excessive backtracking while synchronously processing attacker-controlled URL query strings for HTTP span metadata. A remote attacker can…
When was the CVE record for CVE-2026-116588 published?
The CVE record for CVE-2026-116588 was published on October 26, 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 November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-116588 actively exploited?
CVE-2026-116588 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-116588?
CVE-2026-116588 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-116588?
A fix for CVE-2026-116588 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-116588 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-116588

Explore →

Is Your Infrastructure Affected by CVE-2026-116588?

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