Pillow is a Python imaging library. Prior to 12.3.0, Pillow public image coordinate APIs can trigger a native heap out-of-bounds write when given coordinates near the signed 32-bit integer limits in Image.paste(), Image.crop(), or Image.alpha_composite(). This issue is fixed in version 12.3.0.
CVE-2026-59199
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% 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
- 31%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026Heap out-of-bounds write in Pillow `Image.paste()` / `Image.crop()` via signed coordinate overflow · Advisory · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/security/advisories/GHSA-6r8x-57c9-28j412.3.0
Patch available: python-pillow/Pillow 12.3.0
https://github.com/python-pillow/Pillow/releases/tag/12.3.0Use int64_t to calculate paste box dimensions
Patch available: python-pillow/Pillow 12.3.0 (PR #9703 merged 2026-06-22)
https://github.com/python-pillow/Pillow/pull/9703commit ceefc348eb3c (python-pillow/Pillow)
Patch available: python-pillow/Pillow 12.3.0 (contains commit ceefc348eb3c)
https://github.com/python-pillow/Pillow/commit/ceefc348eb3c3844c7f9796ef2cc3a7dd5fbba7bVendor Advisories for CVE-2026-59199(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-6r8x-57c9-28j4GitHub Security AdvisoriesHigh
Pillow: Heap out-of-bounds write `Image.paste()` / `Image.crop()` via signed coordinate overflow
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 | 1.0 ... 9.5.0 (106 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 23× in last 7d / 110× 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 142 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-28 02:02 UTCEG score recompute
- 2026-08-28 02:02 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 13:51 UTCVendor advisory
- 2026-08-27 01:25 UTCEG score recompute
- 2026-08-27 01:25 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 13:48 UTCVendor advisory
- 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 09:32 UTCVendor advisory
- 2026-08-24 21:43 UTCEG score recompute
- 2026-08-24 21:43 UTCVendor advisory
- 2026-08-24 09:55 UTCEG score recompute
- 2026-08-24 09:55 UTCVendor advisory
- 2026-08-23 22:17 UTCVendor advisory
- 2026-08-23 10:25 UTCEG score recompute
- 2026-08-23 10:25 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 22:46 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-22 11:08 UTCEG score recompute
- 2026-08-22 11:08 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 23:29 UTCVendor advisory
- 2026-08-21 11:48 UTCVendor advisory
- 2026-08-20 23:54 UTCEG score recompute
- 2026-08-20 23:54 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 12:17 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:56 UTCVendor advisory
- 2026-08-18 22:18 UTCEG score recompute
- 2026-08-18 22:18 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 10:20 UTCVendor advisory
- 2026-08-17 21:29 UTCEG score recompute
- 2026-08-17 21:29 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 09:51 UTCVendor advisory
- 2026-08-16 22:14 UTCEG score recompute
- 2026-08-16 22:14 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 10:37 UTCEG score recompute
- 2026-08-16 10:37 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 23:00 UTCVendor advisory
- 2026-08-15 11:23 UTCEG score recompute
- 2026-08-15 11:23 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:45 UTCVendor advisory
- 2026-08-14 12:08 UTCVendor advisory
- 2026-08-14 00:31 UTCEG score recompute
- 2026-08-14 00:31 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 12:53 UTCVendor advisory
- 2026-08-13 01:16 UTCEG score recompute
- 2026-08-13 01:16 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 13:39 UTCVendor advisory
- 2026-08-12 02:01 UTCVendor advisory
- 2026-08-11 14:23 UTCEG score recompute
- 2026-08-11 14:23 UTCVendor advisory
- 2026-08-11 02:45 UTCEG score recompute
- 2026-08-11 02:45 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 15:08 UTCVendor advisory
- 2026-08-10 03:30 UTCVendor advisory
- 2026-08-09 15:53 UTCEG score recompute
- 2026-08-09 15:53 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 04:16 UTCVendor advisory
- 2026-08-08 16:39 UTCEG score recompute
- 2026-08-08 16:39 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 05:01 UTCVendor advisory
- 2026-08-07 17:24 UTCEG score recompute
- 2026-08-07 17:24 UTCVendor advisory
- 2026-08-07 05:47 UTCVendor advisory
- 2026-08-06 18:10 UTCEG score recompute
- 2026-08-06 18:10 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 06:33 UTCEG score recompute
- 2026-08-06 06:33 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 18:56 UTCVendor advisory
- 2026-08-05 07:18 UTCVendor advisory
- 2026-08-04 19:40 UTCEG score recompute
- 2026-08-04 19:40 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 08:00 UTCVendor advisory
- 2026-08-03 19:48 UTCEG score recompute
- 2026-08-03 19:48 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-190 · CWE-787
Frequently asked(5)
What is CVE-2026-59199?
When was CVE-2026-59199 disclosed?
Is CVE-2026-59199 actively exploited?
What is the CVSS score of CVE-2026-59199?
How do I remediate CVE-2026-59199?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59199
Is Your Infrastructure Affected by CVE-2026-59199?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.