CVE-2026-59205

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-20. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-43746 (ENISA EUVD) · GHSA-9hw9-ch79-4vh6 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

October 24, 2026

Advisory Details (4)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

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 pull request 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

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatquay/quay-rhel9:17912655902026-10-12redhat
redhatrhelai3/bootc-rocm-rhel9:17906144472026-10-05redhat
redhatrhelai3/disk-image-cuda-rhel9:17909574172026-10-05redhat
redhatrhoai/odh-llm-d-inference-scheduler-rhel9:17896624302026-09-30redhat
redhatrhaii/vllm-rocm-rhel9:17901096202026-09-23redhat
redhatrhaii/vllm-cpu-rhel9:17900757932026-09-23redhat
redhatrhaii/vllm-spyre-rhel9:17900761412026-09-23redhat
redhatrhaii/model-opt-cuda-rhel9:17900764982026-09-23redhat
redhatrhaii/vllm-cuda-rhel9:17900901312026-09-23redhat
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatrhaii/vllm-rocm-rhel9:17896811262026-09-21redhat
redhatrhaii/model-opt-cuda-rhel9:17896811262026-09-21redhat
redhatrhaii/vllm-cuda-rhel9:17896811262026-09-21redhat
redhatrhaii/vllm-cpu-rhel9:17896811282026-09-21redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
redhatrhaii/vllm-spyre-rhel9:17896812012026-09-21redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17882739772026-09-01redhat
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhaiis/vllm-rocm-rhel9:17878848732026-08-31redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatrhaiis/model-opt-cuda-rhel9:17877721572026-08-31redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhaiis/model-opt-cuda-rhel9:17876011592026-08-25redhat
redhatquay/quay-rhel9:17861819812026-08-12redhat
redhatquay/quay-rhel8:17863950652026-08-11redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatquay/quay-rhel8:17859500042026-08-05redhat
redhatquay/quay-rhel8:17852615062026-07-30redhat
pippillow @ 12.3.0 (fixes < 12.3.0)—ghsa

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.

Additional Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 11× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 232 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-59205?
CVE-2026-59205 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-59205 published?
The CVE record for CVE-2026-59205 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-59205 actively exploited?
CVE-2026-59205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59205?
CVE-2026-59205 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-59205?
A fix for CVE-2026-59205 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59205 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-59205

Explore →

Is Your Infrastructure Affected by CVE-2026-59205?

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