Pillow is a Python imaging library. Prior to 13.0.0 on Windows, src/PIL/WmfImagePlugin.py passes unchecked 32-bit WMF or EMF dimensions to the native drawwmf handler in src/display.c. The handler sizes a DIB allocation from 16-bit-truncated bcWidth and bcHeight fields but copies pixel data using the original full dimensions. A crafted wide, short metafile can pass the pixel-count decompression-bomb check and make the Windows-only renderer read beyond the heap buffer, potentially disclosing memory or crashing the process. This issue is fixed in version 13.0.0.
CVE-2026-96644
HIGHNVD 8.18.1Trending — 4 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Also known asEUVD-2026-107563 (ENISA EUVD) · GHSA-9v9v-9qvf-h2hj (GitHub Security Advisories)Source: ENISA EUVD
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 8.1HIGHmedium confidence
- EG Risk
- 52EG Risk 52/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)Severity81% × 45%Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (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. - EPSS PROB
- 0.4%
- EPSS %ILE
- 32nd
- 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.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 21, 2026
Last Modified
October 28, 2026
Advisory Details (4)
Auto-updated Oct 21, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available
Heap over-read in WMF/EMF rendering via 16-bit dimension truncation (Windows builds) · Advisory · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/security/advisories/GHSA-9v9v-9qvf-h2hjGitHub release Patch Available
13.0.0
Patch available: python-pillow/Pillow 13.0.0
https://github.com/python-pillow/Pillow/releases/tag/13.0.0GitHub pull request Patch Available
Limit WMF dimensions when loading to 0-65535
Patch available: python-pillow/Pillow 13.0.0 (PR #10120 merged 2026-10-04)
https://github.com/python-pillow/Pillow/pull/10120GitHub commit Patch Available
commit 4cf46bee3383 (python-pillow/Pillow)
Patch available: python-pillow/Pillow 13.0.0 (contains commit 4cf46bee3383)
https://github.com/python-pillow/Pillow/commit/4cf46bee338304c5c8968fd7f132ba0d40c428b7Vendor Advisories for CVE-2026-96644(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 | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | Pillow @ 13.0.0 (fixes < 13.0.0) | — | 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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pillow | 1.0 ... 9.5.0 (107 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 22× 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.
- 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-11-01 07:37 UTCGHSA enrichmentGHSA-9v9v-9qvf-h2hj · GitHub severity HIGH
- 2026-11-01 07:37 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-28 19:25 UTCEG score recompute
- 2026-10-28 18:35 UTCEG score recompute
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-27 14:48 UTCEG score recompute▲ 1.00
- 2026-10-27 14:46 UTCNVD updateCVSS v3 → 8.1
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-25 13:48 UTCEG score recompute
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-22 17:07 UTCEG score recompute
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-21 21:27 UTCEG score recompute
- 2026-10-21 21:02 UTCEG score recomputeFirst assessed: 7.1 HIGH
- 2026-10-21 21:02 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:pillow
Frequently asked(5)
What is CVE-2026-96644?
CVE-2026-96644 is a high-severity vulnerability; its CVE record was published on October 21, 2026. Pillow is a Python imaging library. Prior to 13.0.0 on Windows, src/PIL/WmfImagePlugin.py passes unchecked 32-bit WMF or EMF dimensions to the native drawwmf handler in src/display.c. The handler sizes a DIB allocation from 16-bit-truncated bcWidth and bcHeight fields but copies pixel data using…
When was the CVE record for CVE-2026-96644 published?
The CVE record for CVE-2026-96644 was published on October 21, 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 October 28, 2026; the record at its source may have been updated since.
Is CVE-2026-96644 actively exploited?
CVE-2026-96644 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96644?
CVE-2026-96644 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-96644?
A fix for CVE-2026-96644 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-96644 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-96644
Is Your Infrastructure Affected by CVE-2026-96644?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.