Pillow is a Python imaging library. From 8.2.0 through 12.2.0, src/libImaging/Jpeg2KDecode.c accumulates total_component_width across every tile in a JPEG2000 image instead of recomputing it per tile, allowing a crafted tiled JPEG2000 file to force substantially higher transient memory usage and trigger out-of-memory failures during decoding. This issue is fixed in version 12.3.0.
CVE-2026-59204
This high-severity CVE scores 7.5 under NVD CVSS v3. 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
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
- 32%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 21, 2026
Advisory Details (4)
Auto-updated Jul 14, 202612.3.0
Patch available: python-pillow/Pillow 12.3.0
https://github.com/python-pillow/Pillow/releases/tag/12.3.0commit 13ada4117214 (python-pillow/Pillow)
Patch available: python-pillow/Pillow 12.3.0 (contains commit 13ada4117214)
https://github.com/python-pillow/Pillow/commit/13ada41172142f2fd9f0906f615a00ea623a11caCalculate JPEG2000 total_component_width for each tile in isolation
Patch available: python-pillow/Pillow 12.3.0 (PR #9704 merged 2026-06-22)
https://github.com/python-pillow/Pillow/pull/9704Pillow JPEG2000 tiled decode retains a growing scratch buffer and can be used for denial of service · Advisory · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/security/advisories/GHSA-vjc4-5qp5-m44jVendor Advisories for CVE-2026-59204(6)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:60520Red Hat Product SecurityCritical
Red Hat Security Advisory: RHOAI 3.4.4 - Red Hat OpenShift AI
- RHSA-2026:53520Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.10.25
- RHSA-2026:52968Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.12.21
- RHSA-2026:50931Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.9.25
- RHSA-2026:48933Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.15.7
- GHSA-vjc4-5qp5-m44jGitHub Security AdvisoriesHigh
Pillow JPEG2000 tiled decode retains a growing scratch buffer and can be used for denial of service
Patch Availability(6)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:1787073593 | 2026-08-27 | redhat |
| redhat | rhaiis/model-opt-cuda-rhel9:1787601159 | 2026-08-25 | redhat |
| redhat | quay/quay-rhel8:1786395065 | 2026-08-11 | redhat |
| redhat | quay/quay-rhel8:1786170635 | 2026-08-10 | redhat |
| redhat | quay/quay-rhel8:1785950004 | 2026-08-05 | redhat |
| redhat | quay/quay-rhel8:1785261506 | 2026-07-30 | 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 | 10.0.0 ... 9.5.0 (27 versions) | 12.3.0 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 19× in last 7d / 103× 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 136 total refreshes for this CVE.
- 2026-08-30 05:24 UTCEG score recompute
- 2026-08-30 05:24 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 21:33 UTCEG score recompute
- 2026-08-27 21:33 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 03:56 UTCVendor advisory
- 2026-08-26 15:00 UTCEG score recompute
- 2026-08-26 15:00 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 01:46 UTCEG score recompute
- 2026-08-26 01:46 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 11:04 UTCVendor advisory
- 2026-08-24 22:11 UTCEG score recompute
- 2026-08-24 22:11 UTCVendor advisory
- 2026-08-24 09:16 UTCVendor advisory
- 2026-08-23 20:06 UTCVendor advisory
- 2026-08-23 07:15 UTCEG score recompute
- 2026-08-23 07:15 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 18:23 UTCVendor advisory
- 2026-08-22 05:31 UTCEG score recompute
- 2026-08-22 05:31 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 16:40 UTCVendor advisory
- 2026-08-21 03:33 UTCEG score recompute
- 2026-08-21 03:33 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 14:40 UTCVendor advisory
- 2026-08-20 00:33 UTCEG score recompute
- 2026-08-20 00:33 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 09:14 UTCVendor advisory
- 2026-08-18 20:04 UTCEG score recompute
- 2026-08-18 20:04 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 04:23 UTCVendor advisory
- 2026-08-17 15:19 UTCEG score recompute
- 2026-08-17 15:19 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 02:28 UTCEG score recompute
- 2026-08-17 02:28 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:36 UTCEG score recompute
- 2026-08-16 13:36 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 00:45 UTCVendor advisory
- 2026-08-15 11:54 UTCEG score recompute
- 2026-08-15 11:54 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:03 UTCVendor advisory
- 2026-08-14 10:12 UTCEG score recompute
- 2026-08-14 10:12 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 21:20 UTCVendor advisory
- 2026-08-13 08:27 UTCVendor advisory
- 2026-08-12 19:36 UTCEG score recompute
- 2026-08-12 19:36 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 06:45 UTCVendor advisory
- 2026-08-11 17:54 UTCEG score recompute
- 2026-08-11 17:54 UTCVendor advisory
- 2026-08-11 05:03 UTCEG score recompute
- 2026-08-11 05:03 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 16:11 UTCVendor advisory
- 2026-08-10 02:44 UTCVendor advisory
- 2026-08-09 13:53 UTCEG score recompute
- 2026-08-09 13:53 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 01:02 UTCEG score recompute
- 2026-08-09 01:02 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 12:10 UTCVendor advisory
- 2026-08-07 23:18 UTCEG score recompute
- 2026-08-07 23:18 UTCVendor advisory
- 2026-08-07 10:27 UTCVendor advisory
- 2026-08-06 21:36 UTCEG score recompute
- 2026-08-06 21:36 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 08:44 UTCVendor advisory
- 2026-08-05 19:53 UTCEG score recompute
- 2026-08-05 19:53 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 07:02 UTCVendor advisory
- 2026-08-04 18:09 UTCEG score recompute
- 2026-08-04 18:09 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 05:12 UTCVendor advisory
- 2026-08-03 16:14 UTCEG score recompute
- 2026-08-03 16:14 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 03:22 UTCVendor advisory
- 2026-08-02 14:30 UTCEG score recompute
- 2026-08-02 14:30 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-02 01:38 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-770
Frequently asked(5)
What is CVE-2026-59204?
When was CVE-2026-59204 disclosed?
Is CVE-2026-59204 actively exploited?
What is the CVSS score of CVE-2026-59204?
How do I remediate CVE-2026-59204?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59204
Is Your Infrastructure Affected by CVE-2026-59204?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.