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.
CVE-2026-7210
Score 9.8 from GitHub Security Advisory published 2026-05-11. NVD baseline CVSS 7.5; sources differ by 2.3.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- 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 computedSeverity98% × 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, 2026oss-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/8oss-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/13Mailman 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/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[CVE-2026-7210] Insufficient entropy in `pyexpat` with protection against hash flooding · Issue #149018 · python/cpython · GitHub
https://github.com/python/cpython/issues/149018Vendor Advisories for CVE-2026-7210(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | python3.5-venv (3.5.2-2ubuntu0~16.04.13+esm23) @ xenial | 2026-08-23 | ubuntu |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python2.7 | 2.7.18-10 ... 2.7.18-9 (10 versions) | — | — |
| python3.9 | 3.9.10-1 ... 3.9.9-4 (29 versions) | — | — |
Debian:14(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python3.13 | 3.13.11-1 ... 3.13.9-1 (7 versions) | 3.13.14-1 | — |
| python3.14 | 3.14.0-1 ... 3.14.5~rc1-1 (23 versions) | 3.14.6-1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python3.11 | 3.11.2-6 ... 3.11.9-1 (28 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python3.13 | 3.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.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:18 UTCEPSS rescore
- 2026-08-23 18:37 UTCEG score recompute
- 2026-08-23 18:37 UTCVendor advisory
- 2026-08-23 18:37 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 14:42 UTCEG score recompute
- 2026-08-17 14:42 UTCVendor advisory
- 2026-08-17 14:42 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 11:03 UTCEG score recompute
- 2026-08-17 11:03 UTCVendor advisory
- 2026-08-17 11:03 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:43 UTCVendor advisory
- 2026-08-16 11:43 UTCGHSA enrichment
- 2026-08-16 08:04 UTCVendor advisory
- 2026-08-16 08:04 UTCGHSA enrichment
- 2026-08-16 04:25 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-16 04:25 UTCVendor advisory
- 2026-08-16 04:25 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 23:08 UTCVendor advisory
- 2026-08-14 23:08 UTCGHSA enrichment
- 2026-08-14 19:30 UTCVendor advisory
- 2026-08-14 19:30 UTCGHSA enrichment
- 2026-08-14 15:52 UTCVendor advisory
- 2026-08-14 15:52 UTCGHSA enrichment
- 2026-08-14 12:14 UTCVendor advisory
- 2026-08-14 12:14 UTCGHSA enrichment
- 2026-08-14 08:37 UTCVendor advisory
- 2026-08-14 08:37 UTCGHSA enrichment
- 2026-08-14 04:59 UTCVendor advisory
- 2026-08-14 04:59 UTCGHSA enrichment
- 2026-08-14 01:21 UTCVendor advisory
- 2026-08-14 01:21 UTCGHSA enrichment
- 2026-08-14 00:48 UTCEG score recompute
- 2026-08-14 00:48 UTCVendor advisory
- 2026-08-14 00:48 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 09:35 UTCVendor advisory
- 2026-08-13 09:35 UTCGHSA enrichment
- 2026-08-13 05:57 UTCVendor advisory
- 2026-08-13 05:57 UTCGHSA enrichment
- 2026-08-13 01:23 UTCVendor advisory
- 2026-08-13 01:23 UTCGHSA enrichment
- 2026-08-13 00:41 UTCVendor advisory
- 2026-08-13 00:41 UTCGHSA enrichment
- 2026-08-12 23:45 UTCVendor advisory
- 2026-08-12 23:45 UTCGHSA enrichment
- 2026-08-12 20:07 UTCVendor advisory
- 2026-08-12 20:07 UTCGHSA enrichment
- 2026-08-12 16:29 UTCEG score recompute
- 2026-08-12 16:29 UTCVendor advisory
- 2026-08-12 16:29 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 01:20 UTCVendor advisory
- 2026-08-12 01:20 UTCGHSA enrichment
- 2026-08-12 00:40 UTCVendor advisory
- 2026-08-12 00:40 UTCGHSA enrichment
- 2026-08-11 23:02 UTCVendor advisory
- 2026-08-11 23:01 UTCGHSA enrichment
- 2026-08-11 19:23 UTCVendor advisory
- 2026-08-11 19:23 UTCGHSA enrichment
- 2026-08-11 15:46 UTCEG score recompute
- 2026-08-11 15:46 UTCVendor advisory
- 2026-08-11 15:46 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 08:26 UTCVendor advisory
- 2026-08-11 08:26 UTCGHSA enrichment
- 2026-08-11 04:47 UTCVendor advisory
- 2026-08-11 04:47 UTCGHSA enrichment
- 2026-08-11 01:10 UTCEG score recompute
- 2026-08-11 01:10 UTCVendor advisory
- 2026-08-11 01:10 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 11:54 UTCVendor advisory
- 2026-08-10 11:53 UTCGHSA enrichment
- 2026-08-10 08:16 UTCVendor advisory
- 2026-08-10 08:16 UTCGHSA enrichment
- 2026-08-10 04:37 UTCVendor advisory
- 2026-08-10 04:37 UTCGHSA enrichment
- 2026-08-10 00:59 UTCVendor advisory
- 2026-08-10 00:59 UTCGHSA enrichment
- 2026-08-09 21:21 UTCVendor advisory
- 2026-08-09 21:21 UTCGHSA enrichment
- 2026-08-09 17:43 UTCVendor advisory
- 2026-08-09 17:43 UTCGHSA enrichment
- 2026-08-09 14:06 UTCEG score recompute
- 2026-08-09 14:06 UTCVendor advisory
- 2026-08-09 14:06 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 10:28 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-7210?
When was CVE-2026-7210 disclosed?
Is CVE-2026-7210 actively exploited?
What is the CVSS score of CVE-2026-7210?
How do I remediate CVE-2026-7210?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7210
Is Your Infrastructure Affected by CVE-2026-7210?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.