CVE-2026-59197

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% 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
Trending — Patch released this weekElevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Pillow is a Python imaging library. Prior to 12.3.0, Pillow's public rank-filter API can trigger a native heap out-of-bounds write when given a very large odd filter size because ImageFilter.RankFilter.filter() calls image.expand(size // 2, size // 2) before rank-filter size validation and ImagingExpand() computes output dimensions with unchecked signed int arithmetic. This issue is fixed in version 12.3.0.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
68(Attend)
EG Risk 68/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 computed
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 21, 2026

Advisory Details (4)

Auto-updated Jul 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Heap out-of-bounds write in Pillow `ImageFilter.RankFilter` via integer overflow in `ImagingExpand` · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-xj96-63gp-2gmr
github_release Patch Available

12.3.0

Patch available: python-pillow/Pillow 12.3.0

https://github.com/python-pillow/Pillow/releases/tag/12.3.0
github_pr Patch Available

Validate large filter sizes when initializing RankFilter

Patch available: python-pillow/Pillow 12.3.0 (PR #9695 merged 2026-06-21)

https://github.com/python-pillow/Pillow/pull/9695
github_commit Patch Available

commit cce3bdb867c7 (python-pillow/Pillow)

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

https://github.com/python-pillow/Pillow/commit/cce3bdb867c77a3420261ed1bfdb6b0787ec8fc1

Vendor Advisories for CVE-2026-59197(15)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatpython-pillow-0:5.1.1-20.el8_6.12026-08-13redhat
redhatpython-pillow-0:5.1.1-20.el8_8.12026-08-12redhat
redhatquay/quay-rhel8:17863950652026-08-11redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatpython-pillow-0:5.1.1-15.el8_4.22026-08-10redhat
redhatquay/quay-rhel8:17859500042026-08-05redhat
redhatpython-pillow-0:12.3.0-1.el9pc2026-08-04redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17856461882026-08-04redhat
redhatansible-automation-platform-27/lightspeed-chatbot-rhel9:17854267342026-08-04redhat
redhatpython3.12-pillow-0:12.3.0-1.el9ap2026-08-04redhat
redhatquay/quay-rhel8:17852615062026-07-30redhat
redhatpython-pillow-0:5.1.1-23.el8_102026-07-29redhat

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 rangeFixed inDependents
pillow10.0.0-1 ... 9.5.0-1 (38 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pillow10.0.0-1 ... 9.5.0-1 (23 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pillow11.1.0-5 ... 12.3.0-1 (13 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pillow11.1.0-5 ... 12.2.0-1 (8 versions)12.3.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pillow1.0 ... 9.5.0 (106 versions)12.3.0—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59197?
CVE-2026-59197 is a high vulnerability published on July 14, 2026. Pillow is a Python imaging library. Prior to 12.3.0, Pillow's public rank-filter API can trigger a native heap out-of-bounds write when given a very large odd filter size because ImageFilter.RankFilter.filter() calls image.expand(size // 2, size // 2) before rank-filter size validation and…
When was CVE-2026-59197 disclosed?
CVE-2026-59197 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59197 actively exploited?
CVE-2026-59197 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.0% of all scored CVEs.
What is the CVSS score of CVE-2026-59197?
CVE-2026-59197 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-59197?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59197, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59197

Explore →

Is Your Infrastructure Affected by CVE-2026-59197?

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

Start Free Scan →Browse All CVEs