Pillow is a Python imaging library. Prior to 12.3.0, when Pillow loads an uncompressed McIdas AREA image from a filename through the mmap raw codec path, attacker-controlled header words can set a row stride smaller than the natural row width, causing pixel access such as Image.tobytes(), getpixel, convert, or save to read beyond the mapped region and disclose adjacent process memory or fault. This issue is fixed in version 12.3.0.
CVE-2026-54058
This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). 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
- 8.3
- EG Score
- 8.3(low)
- EPSS
- 30.6%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 14, 2026Out-of-bounds read via attacker-controlled row stride on Pillow's mmap path (McIdas AREA files) · Advisory · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/security/advisories/GHSA-62p4-gmf7-7g9312.3.0
Patch available: python-pillow/Pillow 12.3.0
https://github.com/python-pillow/Pillow/releases/tag/12.3.0Ensure map stride is at least one full row of pixels
Patch available: python-pillow/Pillow 12.3.0 (PR #9719 merged 2026-06-25)
https://github.com/python-pillow/Pillow/pull/9719commit 6a8de891fb00 (python-pillow/Pillow)
Patch available: python-pillow/Pillow 12.3.0 (contains commit 6a8de891fb00)
https://github.com/python-pillow/Pillow/commit/6a8de891fb00968e5ea79bfa84368ed90b3cfc1dWeakness Classification(1)
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 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 15:05 UTCEG score recompute
- 2026-07-15 03:52 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-125
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-2015-9290EG 9.8CRITICAL
- CVE-2016-10749EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS 96%CRITICAL
- CVE-2014-3180EG 9.1CRITICAL
- CVE-2014-1508EG 9.1EPSS 90%CRITICAL
- CVE-2016-5198NVD 8.8EG 9.0 KEVEPSS 98%HIGH
- CVE-2016-4523NVD 7.5EG 9.0 KEVEPSS 98%HIGH
Frequently asked(5)
What is CVE-2026-54058?
When was CVE-2026-54058 disclosed?
Is CVE-2026-54058 actively exploited?
What is the CVSS score of CVE-2026-54058?
How do I remediate CVE-2026-54058?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54058
Is Your Infrastructure Affected by CVE-2026-54058?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.