CVE-2026-7210

CRITICALNVD 7.59.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory published 2026-05-11. NVD baseline CVSS 7.5; sources differ by 2.3.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

xml.parsers.expat and xml.etree.ElementTree use insufficient entropy for Expat hash-flooding protection, which allows a crafted XML document to trigger hash flooding.\r\n\r\nFully mitigating this vulnerability requires both updating libexpat to 2.8.0 or later and applying this patch.

CVSS v3
7.5
EG Score
9.8CRITICALmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.4%
EPSS %ILE
70th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 11, 2026

Last Modified

October 2, 2026

Advisory Details (5)

Auto-updated May 16, 2026
Patch available.
generic

oss-security - [CVE-2026-7210] Cpython: The expat and elementtree parsers use insufficient entropy for XML hash-flooding protection

http://www.openwall.com/lists/oss-security/2026/05/11/8
generic

oss-security - Re: [CVE-2026-7210] Cpython: The expat and elementtree parsers use insufficient entropy for XML hash-flooding protection

http://www.openwall.com/lists/oss-security/2026/05/11/13
generic

Mailman 3 [CVE-2026-7210] The expat and elementtree parsers use insufficient entropy for XML hash-flooding protection - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/PNY5OMBDPM2FRUZTWFFPJ6LISWKV627K/
generic

gh-149018: Use `XML_SetHashSalt16Bytes` in `pyexpat`/`_elementtree` when possible by StanFromIreland · Pull Request #149023 · python/cpython · GitHub

https://github.com/python/cpython/pull/149023
generic

[CVE-2026-7210] Insufficient entropy in `pyexpat` with protection against hash flooding · Issue #149018 · python/cpython · GitHub

https://github.com/python/cpython/issues/149018

Vendor Advisories for CVE-2026-7210(6)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3.5-venv (3.5.2-2ubuntu0~16.04.13+esm23) @ xenial2026-10-02ubuntu
redhatpython3-10-main-3.10.21-1.4.hum12026-09-18redhat
redhatpython3-13-main-3.13.15-1.3.hum12026-09-16redhat
redhatpython3-11-main-3.11.16-1.4.hum12026-09-16redhat
redhatpython3-12-main-3.12.14-1.3.hum12026-09-16redhat
redhatpython3-14-main-3.14.7-1.2.hum12026-09-15redhat

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

(10 across 8 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
python2.72.7.18-10 ... 2.7.18-9 (10 versions)
  • every version on: no fix on record
—
python3.93.9.10-1 ... 3.9.9-4 (29 versions)
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
python3.133.13.11-1 ... 3.13.9-1 (7 versions)
  • every version up to 3.13.14-1: fixed in 3.13.14-1
—
python3.143.14.0-1 ... 3.14.5~rc1-1 (23 versions)
  • every version up to 3.14.6-1: fixed in 3.14.6-1
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.14.7-r0: fixed in 3.14.7-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python3.113.11.2-6 ... 3.11.9-1 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python3.133.13.11-1 ... 3.13.9-1 (14 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Showing the most recent 100 of 425 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

2 shown

redhat:RHSA-2026:68135 · redhat:RHSA-2026:67572

Frequently asked(5)

What is CVE-2026-7210?
CVE-2026-7210 is a critical vulnerability published on May 11, 2026. xml.parsers.expat and xml.etree.ElementTree use insufficient entropy for Expat hash-flooding protection, which allows a crafted XML document to trigger hash flooding.\r\n\r\nFully mitigating this vulnerability requires both updating libexpat to 2.8.0 or later and applying this patch.
When was CVE-2026-7210 disclosed?
CVE-2026-7210 was first published on May 11, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7210 actively exploited?
CVE-2026-7210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-7210?
CVE-2026-7210 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2026-7210?
A fix for CVE-2026-7210 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-7210 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-7210

Explore →

Is Your Infrastructure Affected by CVE-2026-7210?

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

Book a Demo →Browse All CVEs