CVE-2026-59204

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — Patch released 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. 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.

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 21, 2026

Advisory Details (4)

Auto-updated Jul 14, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
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_commit Patch Available

commit 13ada4117214 (python-pillow/Pillow)

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

https://github.com/python-pillow/Pillow/commit/13ada41172142f2fd9f0906f615a00ea623a11ca
github_pr Patch Available

Calculate 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/9704
github Patch Available🟡 PoC Available

Pillow 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-m44j

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
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
pillow10.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.

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

Frequently asked(5)

What is CVE-2026-59204?
CVE-2026-59204 is a high vulnerability published on July 14, 2026. Pillow is a Python imaging library. From 8.2.0 through 12.2.0, src/libImaging/Jpeg2KDecode.c accumulates totalcomponentwidth 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…
When was CVE-2026-59204 disclosed?
CVE-2026-59204 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-59204 actively exploited?
CVE-2026-59204 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-59204?
CVE-2026-59204 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59204?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59204, 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-59204

Explore →

Is Your Infrastructure Affected by CVE-2026-59204?

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