CVE-2026-54059

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
githubMentions a patch (unverified)🟡 PoC Available

PcfFontFile._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-wr9x
github_commit Patch Available

commit 0a263e6264aa (python-pillow/Pillow)

Patch available: python-pillow/Pillow 12.3.0 (contains commit 0a263e6264aa)

https://github.com/python-pillow/Pillow/commit/0a263e6264aa5399988d9acd3bbfbca2ca3ec77d
generic

Pillow/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.rst

Vendor 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.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython-pillow-0:5.1.1-15.el8_4.22026-08-10redhat
redhatpython3.12-pillow-0:12.3.0-1.el9ap2026-08-04redhat
redhatpython-pillow-0:12.3.0-1.el9pc2026-08-04redhat
redhatpython3.12-pillow-0:12.3.0-1.el9pc2026-08-04redhat
redhatpython-pillow-0:5.1.1-20.el8_82026-07-31redhat
redhatpython-pillow-0:5.1.1-20.el8_62026-07-31redhat
redhatpython-pillow-0:5.1.1-22.el8_102026-07-14redhat

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)
PackageVulnerable rangeFix by version rangeDependents
pillow10.0.0-1 ... 9.5.0-1 (38 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pillow10.0.0-1 ... 9.5.0-1 (23 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5 ... 12.3.0-1 (13 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5 ... 12.2.0-1 (8 versions)
  • every version up to 12.3.0-1: fixed in 12.3.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pillow1.0 ... 9.5.0 (106 versions)
  • every version up to 12.3.0: fixed in 12.3.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 35× 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 215 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 06:23 UTCEG score recompute
  18. 2026-09-23 06:23 UTCVendor advisory
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 06:00 UTCEG score recompute
  22. 2026-09-18 06:00 UTCVendor advisory
  23. 2026-09-17 19:31 UTCEPSS rescore
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 75 more
  1. 2026-09-14 11:40 UTCVendor advisory
  2. 2026-09-13 23:56 UTCEG score recompute
  3. 2026-09-13 23:56 UTCVendor advisory
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-13 08:43 UTCEG score recompute
  6. 2026-09-13 08:43 UTCVendor advisory
  7. 2026-09-12 13:37 UTCEG score recompute
  8. 2026-09-12 13:37 UTCVendor advisory
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-10 09:35 UTCEPSS rescore
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 14:10 UTCEG score recompute
  14. 2026-09-06 14:10 UTCVendor advisory
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 23:11 UTCEG score recompute
  17. 2026-09-05 23:11 UTCVendor advisory
  18. 2026-09-04 05:06 UTCEPSS rescore
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 13:54 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-08-30 19:21 UTCEG score recompute
  23. 2026-08-30 19:21 UTCVendor advisory
  24. 2026-08-30 19:17 UTCEPSS rescore
  25. 2026-08-30 08:14 UTCEG score recompute
  26. 2026-08-30 08:14 UTCVendor advisory
  27. 2026-08-30 01:22 UTCEPSS rescore
  28. 2026-08-28 21:41 UTCEPSS rescore
  29. 2026-08-27 21:58 UTCEG score recompute
  30. 2026-08-27 21:58 UTCVendor advisory
  31. 2026-08-27 14:25 UTCEPSS rescore
  32. 2026-08-27 02:16 UTCEG score recompute
  33. 2026-08-27 02:16 UTCVendor advisory
  34. 2026-08-26 14:46 UTCEPSS rescore
  35. 2026-08-26 13:55 UTCEG score recompute
  36. 2026-08-26 13:55 UTCVendor advisory
  37. 2026-08-25 13:49 UTCEPSS rescore
  38. 2026-08-25 13:33 UTCVendor advisory
  39. 2026-08-25 02:21 UTCVendor advisory
  40. 2026-08-24 15:13 UTCEG score recompute
  41. 2026-08-24 15:13 UTCVendor advisory
  42. 2026-08-24 04:05 UTCVendor advisory
  43. 2026-08-23 16:19 UTCVendor advisory
  44. 2026-08-23 05:09 UTCEG score recompute
  45. 2026-08-23 05:09 UTCVendor advisory
  46. 2026-08-23 00:19 UTCEPSS rescore
  47. 2026-08-22 18:02 UTCVendor advisory
  48. 2026-08-22 04:48 UTCEG score recompute
  49. 2026-08-22 04:48 UTCVendor advisory
  50. 2026-08-21 23:49 UTCEPSS rescore
  51. 2026-08-21 15:25 UTCVendor advisory
  52. 2026-08-21 04:18 UTCEG score recompute
  53. 2026-08-21 04:18 UTCVendor advisory
  54. 2026-08-20 22:55 UTCEPSS rescore
  55. 2026-08-20 15:48 UTCVendor advisory
  56. 2026-08-20 02:28 UTCEG score recompute
  57. 2026-08-20 02:28 UTCVendor advisory
  58. 2026-08-19 17:04 UTCEPSS rescore
  59. 2026-08-19 09:49 UTCVendor advisory
  60. 2026-08-18 22:29 UTCEG score recompute
  61. 2026-08-18 22:29 UTCVendor advisory
  62. 2026-08-18 13:48 UTCEPSS rescore
  63. 2026-08-18 10:58 UTCVendor advisory
  64. 2026-08-17 22:41 UTCEG score recompute
  65. 2026-08-17 22:41 UTCVendor advisory
  66. 2026-08-17 13:47 UTCEPSS rescore
  67. 2026-08-17 06:48 UTCVendor advisory
  68. 2026-08-16 19:41 UTCEG score recompute
  69. 2026-08-16 19:41 UTCVendor advisory
  70. 2026-08-16 14:56 UTCEPSS rescore
  71. 2026-08-16 07:47 UTCEG score recompute
  72. 2026-08-16 07:47 UTCVendor advisory
  73. 2026-08-16 02:14 UTCEPSS rescore
  74. 2026-08-15 20:40 UTCVendor advisory
  75. 2026-08-15 09:33 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-54059?
CVE-2026-54059 is a high vulnerability published on July 6, 2026. Pillow is a Python imaging library. Prior to 12.3.0, PIL/PcfFontFile.py loadbitmaps() read glyph dimensions from the PCF METRICS section and passed them directly to Image.frombytes() without calling Image.decompressionbomb_check(), allowing crafted PCF font data to cause excessive memory…
When was CVE-2026-54059 disclosed?
CVE-2026-54059 was first published on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54059 actively exploited?
CVE-2026-54059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54059?
CVE-2026-54059 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54059?
A fix for CVE-2026-54059 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54059 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-54059

Explore →

Is Your Infrastructure Affected by CVE-2026-54059?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs