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
Trending — 4 sources updated this week
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%CVSS: 7.5Exploit: None knownExposed: 0

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.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

May 11, 2026

Last Modified

August 14, 2026

Advisory Details (5)

Auto-updated May 16, 2026
No patch confirmed yet.
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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.5-venv (3.5.2-2ubuntu0~16.04.13+esm23) @ xenial2026-08-23ubuntu

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

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
python2.72.7.18-10 ... 2.7.18-9 (10 versions)
python3.93.9.10-1 ... 3.9.9-4 (29 versions)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
python3.133.13.11-1 ... 3.13.9-1 (7 versions)3.13.14-1
python3.143.14.0-1 ... 3.14.5~rc1-1 (23 versions)3.14.6-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python3.113.11.2-6 ... 3.11.9-1 (28 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python3.133.13.11-1 ... 3.13.9-1 (12 versions)

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 183× 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 379 total refreshes for this CVE.

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

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 in the National Vulnerability Database on May 11, 2026, with the most recent update on August 14, 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% probability of exploitation in the next 30 days, which ranks it in the top 50.7% of all 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.
How do I remediate CVE-2026-7210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7210, 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

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.