CVE-2026-54058

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 58% 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
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Pillow is a Python imaging library. Prior to 12.3.0, when Pillow loads an uncompressed McIdas AREA image from a filename through the mmap raw codec path, attacker-controlled header words can set a row stride smaller than the natural row width, causing pixel access such as Image.tobytes(), getpixel, convert, or save to read beyond the mapped region and disclose adjacent process memory or fault. This issue is fixed in version 12.3.0.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

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
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 6, 2026

Advisory Details (4)

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

Out-of-bounds read via attacker-controlled row stride on Pillow's mmap path (McIdas AREA files) · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-62p4-gmf7-7g93
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

Ensure map stride is at least one full row of pixels

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

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

commit 6a8de891fb00 (python-pillow/Pillow)

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

https://github.com/python-pillow/Pillow/commit/6a8de891fb00968e5ea79bfa84368ed90b3cfc1d

Vendor Advisories for CVE-2026-54058(12)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhaiis/model-opt-cuda-rhel9:17876011592026-08-25redhat
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
redhatpython-pillow-0:5.1.1-15.el8_4.22026-08-10redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatquay/quay-rhel8:17859500042026-08-05redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17856461882026-08-04redhat
redhatansible-automation-platform-27/lightspeed-chatbot-rhel9:17854267342026-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(1)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-54058?
CVE-2026-54058 is a critical vulnerability published on July 14, 2026. Pillow is a Python imaging library. Prior to 12.3.0, when Pillow loads an uncompressed McIdas AREA image from a filename through the mmap raw codec path, attacker-controlled header words can set a row stride smaller than the natural row width, causing pixel access such as Image.tobytes(), getpixel,…
When was CVE-2026-54058 disclosed?
CVE-2026-54058 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54058 actively exploited?
CVE-2026-54058 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.0% of all scored CVEs.
What is the CVSS score of CVE-2026-54058?
CVE-2026-54058 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-54058?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54058, 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-54058

Explore →

Is Your Infrastructure Affected by CVE-2026-54058?

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

Start Free Scan →Browse All CVEs