Pillow is a Python imaging library. From 12.0.0 through 12.2.0, Pillow's EPS parser in PIL/EpsImagePlugin.py accepts a negative byte count in the %%BeginBinary directive, allowing a crafted EPS file to cause Image.open() to seek backwards to the same directive and parse it repeatedly in an infinite loop. This issue is fixed in version 12.3.0.
CVE-2026-59203
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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
- 7.5
- EG Score
- 7.5(low)
- EPSS
- 31.3%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026Pillow EpsImagePlugin negative %%BeginBinary byte count causes infinite loop denial of service · Advisory · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/security/advisories/GHSA-pg7v-jwj7-p79812.3.0
Patch available: python-pillow/Pillow 12.3.0
https://github.com/python-pillow/Pillow/releases/tag/12.3.0Raise ValueError if EPS BeginBinary bytecount is negative
Patch available: python-pillow/Pillow 12.3.0 (PR #9708 merged 2026-06-22)
https://github.com/python-pillow/Pillow/pull/9708commit 03992618118b (python-pillow/Pillow)
Patch available: python-pillow/Pillow 12.3.0 (contains commit 03992618118b)
https://github.com/python-pillow/Pillow/commit/03992618118b4a76b6163cd72ab5ecd684133b83Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× 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 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 14:43 UTCEG score recompute▲ 2.20
- 2026-07-15 14:22 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-07-15 14:09 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
- 2026-07-14 21:22 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-07-14 16:11 UTCEG score recompute
- 2026-07-14 16:10 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-59203?
When was CVE-2026-59203 disclosed?
Is CVE-2026-59203 actively exploited?
What is the CVSS score of CVE-2026-59203?
How do I remediate CVE-2026-59203?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59203
Is Your Infrastructure Affected by CVE-2026-59203?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.