Pillow is a Python imaging library. Prior to 12.3.0, Pillow's public rank-filter API can trigger a native heap out-of-bounds write when given a very large odd filter size because ImageFilter.RankFilter.filter() calls image.expand(size // 2, size // 2) before rank-filter size validation and ImagingExpand() computes output dimensions with unchecked signed int arithmetic. This issue is fixed in version 12.3.0.
CVE-2026-59197
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EPSS
- 31.9%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 14, 2026Heap out-of-bounds write in Pillow `ImageFilter.RankFilter` via integer overflow in `ImagingExpand` · Advisory · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/security/advisories/GHSA-xj96-63gp-2gmr12.3.0
Patch available: python-pillow/Pillow 12.3.0
https://github.com/python-pillow/Pillow/releases/tag/12.3.0Validate large filter sizes when initializing RankFilter
Patch available: python-pillow/Pillow 12.3.0 (PR #9695 merged 2026-06-21)
https://github.com/python-pillow/Pillow/pull/9695commit cce3bdb867c7 (python-pillow/Pillow)
Patch available: python-pillow/Pillow 12.3.0 (contains commit cce3bdb867c7)
https://github.com/python-pillow/Pillow/commit/cce3bdb867c77a3420261ed1bfdb6b0787ec8fc1Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× 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.
- 2026-07-15 18:16 UTCEG score recompute
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 05:31 UTCEG score recompute
- 2026-07-14 16:40 UTCEG score recompute
- 2026-07-14 16:40 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-787
- CVE-2009-0947EG 9.8CRITICAL
- CVE-2007-0158EG 9.8CRITICAL
- CVE-2007-0899EG 9.8CRITICAL
- CVE-2005-1141EG 9.8CRITICAL
- CVE-2005-0102EG 9.8CRITICAL
- CVE-2002-0391EG 9.8EPSS 99%CRITICAL
- CVE-2002-0639EG 9.8EPSS 97%CRITICAL
- CVE-2010-20115EG 9.3CRITICAL
- CVE-2010-1297NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-3953NVD 8.8EG 9.0 KEVEPSS 100%HIGH
Frequently asked(5)
What is CVE-2026-59197?
When was CVE-2026-59197 disclosed?
Is CVE-2026-59197 actively exploited?
What is the CVSS score of CVE-2026-59197?
How do I remediate CVE-2026-59197?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59197
Is Your Infrastructure Affected by CVE-2026-59197?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.