CVE-2026-59205

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

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
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%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Pillow is a Python imaging library. Prior to 12.3.0, Pillow's ImageCms.ImageCmsTransform.apply(im, imOut) API can trigger controlled native heap corruption when the caller supplies an output image whose mode does not match the transform's declared output mode. This issue is fixed in version 12.3.0.

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 computed
Severity75% × 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 14, 2026

Advisory Details (4)

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

Controlled heap out-of-bounds write in Pillow `ImageCmsTransform.apply()` via output mode mismatch · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-9hw9-ch79-4vh6
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

Raise error if image modes do not match ImageCms transform modes

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

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

commit a9ffc42bedf4 (python-pillow/Pillow)

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

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

Vendor Advisories for CVE-2026-59205(12)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17882739772026-09-01redhat
redhatrhaiis/model-opt-cuda-rhel9:17877721572026-08-31redhat
redhatrhaiis/vllm-rocm-rhel9:17878848732026-08-31redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhaiis/model-opt-cuda-rhel9:17876011592026-08-25redhat
redhatquay/quay-rhel8:17863950652026-08-11redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatquay/quay-rhel8:17859500042026-08-05redhat
redhatquay/quay-rhel8:17852615062026-07-30redhat

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(1)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59205?
CVE-2026-59205 is a high vulnerability published on July 14, 2026. Pillow is a Python imaging library. Prior to 12.3.0, Pillow's ImageCms.ImageCmsTransform.apply(im, imOut) API can trigger controlled native heap corruption when the caller supplies an output image whose mode does not match the transform's declared output mode. This issue is fixed in version 12.3.0.
When was CVE-2026-59205 disclosed?
CVE-2026-59205 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59205 actively exploited?
CVE-2026-59205 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 67.5% of all scored CVEs.
What is the CVSS score of CVE-2026-59205?
CVE-2026-59205 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59205, 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-59205

Explore →

Is Your Infrastructure Affected by CVE-2026-59205?

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

Start Free Scan →Browse All CVEs