Pillow is a Python imaging library. Prior to 12.3.0, PIL/PcfFontFile.py _load_bitmaps() read glyph dimensions from the PCF METRICS section and passed them directly to Image.frombytes() without calling Image._decompression_bomb_check(), allowing crafted PCF font data to cause excessive memory allocation. This issue is fixed in version 12.3.0.
CVE-2026-54059
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% 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
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 7, 2026
Advisory Details (3)
Auto-updated Jul 7, 2026PcfFontFile._load_bitmaps()`: `Image.frombytes()` called without `_decompression_bomb_check()` — bomb protection bypass via PCF font loading · Advisory · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/security/advisories/GHSA-8v84-f9pq-wr9xcommit 0a263e6264aa (python-pillow/Pillow)
Patch available: python-pillow/Pillow 12.3.0 (contains commit 0a263e6264aa)
https://github.com/python-pillow/Pillow/commit/0a263e6264aa5399988d9acd3bbfbca2ca3ec77dPillow/docs/releasenotes/12.3.0.rst at main · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/blob/main/docs/releasenotes/12.3.0.rstVendor Advisories for CVE-2026-54059(11)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:52551Red Hat Product SecurityHigh
Red Hat Security Advisory: python-pillow security update
- RHSA-2026:50336Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update
- RHSA-2026:50319Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update
- RHSA-2026:50263Red Hat Product SecurityHigh
Red Hat Security Advisory: Satellite 6.18.8 Async Update
- RHSA-2026:50223Red Hat Product SecurityHigh
Red Hat Security Advisory: Satellite 6.16.12 Async Update
- RHSA-2026:50222Red Hat Product SecurityHigh
Red Hat Security Advisory: Satellite 6.17.10 Async Update
- RHSA-2026:50221Red Hat Product SecurityHigh
Red Hat Security Advisory: Satellite 6.19.3 Async Update
- RHSA-2026:48759Red Hat Product SecurityHigh
Red Hat Security Advisory: python-pillow security update
- +3 more
Patch Availability(7)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | python-pillow-0:5.1.1-15.el8_4.2 | 2026-08-10 | redhat |
| redhat | python3.12-pillow-0:12.3.0-1.el9ap | 2026-08-04 | redhat |
| redhat | python-pillow-0:12.3.0-1.el9pc | 2026-08-04 | redhat |
| redhat | python3.12-pillow-0:12.3.0-1.el9pc | 2026-08-04 | redhat |
| redhat | python-pillow-0:5.1.1-20.el8_6 | 2026-07-31 | redhat |
| redhat | python-pillow-0:5.1.1-20.el8_8 | 2026-07-31 | redhat |
| redhat | python-pillow-0:5.1.1-22.el8_10 | 2026-07-14 | redhat |
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
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pillow | 10.0.0-1 ... 9.5.0-1 (38 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pillow | 10.0.0-1 ... 9.5.0-1 (23 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pillow | 11.1.0-5 ... 12.3.0-1 (13 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pillow | 11.1.0-5 ... 12.2.0-1 (8 versions) | 12.3.0-1 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pillow | 1.0 ... 9.5.0 (106 versions) | 12.3.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 61× 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 196 total refreshes for this CVE.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 06:00 UTCEG score recompute
- 2026-09-18 06:00 UTCVendor advisory
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 11:40 UTCVendor advisory
- 2026-09-13 23:56 UTCEG score recompute
- 2026-09-13 23:56 UTCVendor advisory
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 08:43 UTCEG score recompute
- 2026-09-13 08:43 UTCVendor advisory
- 2026-09-12 13:37 UTCEG score recompute
- 2026-09-12 13:37 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 14:10 UTCEG score recompute
- 2026-09-06 14:10 UTCVendor advisory
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 23:11 UTCEG score recompute
- 2026-09-05 23:11 UTCVendor advisory
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:21 UTCEG score recompute
- 2026-08-30 19:21 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 08:14 UTCEG score recompute
- 2026-08-30 08:14 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 21:58 UTCEG score recompute
- 2026-08-27 21:58 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 02:16 UTCEG score recompute
- 2026-08-27 02:16 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 13:55 UTCEG score recompute
- 2026-08-26 13:55 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 13:33 UTCVendor advisory
- 2026-08-25 02:21 UTCVendor advisory
- 2026-08-24 15:13 UTCEG score recompute
- 2026-08-24 15:13 UTCVendor advisory
- 2026-08-24 04:05 UTCVendor advisory
- 2026-08-23 16:19 UTCVendor advisory
- 2026-08-23 05:09 UTCEG score recompute
- 2026-08-23 05:09 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 18:02 UTCVendor advisory
- 2026-08-22 04:48 UTCEG score recompute
- 2026-08-22 04:48 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 15:25 UTCVendor advisory
- 2026-08-21 04:18 UTCEG score recompute
- 2026-08-21 04:18 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 15:48 UTCVendor advisory
- 2026-08-20 02:28 UTCEG score recompute
- 2026-08-20 02:28 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 09:49 UTCVendor advisory
- 2026-08-18 22:29 UTCEG score recompute
- 2026-08-18 22:29 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 10:58 UTCVendor advisory
- 2026-08-17 22:41 UTCEG score recompute
- 2026-08-17 22:41 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:48 UTCVendor advisory
- 2026-08-16 19:41 UTCEG score recompute
- 2026-08-16 19:41 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:47 UTCEG score recompute
- 2026-08-16 07:47 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 20:40 UTCVendor advisory
- 2026-08-15 09:33 UTCEG score recompute
- 2026-08-15 09:33 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 22:26 UTCVendor advisory
- 2026-08-14 11:19 UTCVendor advisory
- 2026-08-14 00:11 UTCEG score recompute
- 2026-08-14 00:11 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 13:03 UTCVendor advisory
- 2026-08-13 01:56 UTCVendor advisory
- 2026-08-12 14:49 UTCEG score recompute
- 2026-08-12 14:49 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 03:42 UTCVendor advisory
- 2026-08-11 16:35 UTCEG score recompute
- 2026-08-11 16:35 UTCVendor advisory
- 2026-08-11 05:28 UTCEG score recompute
- 2026-08-11 05:28 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 18:21 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-54059?
When was CVE-2026-54059 disclosed?
Is CVE-2026-54059 actively exploited?
What is the CVSS score of CVE-2026-54059?
How do I remediate CVE-2026-54059?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54059
Is Your Infrastructure Affected by CVE-2026-54059?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.