CVE-2026-54058

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — Patch released this weekElevated
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.5%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

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.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

August 6, 2026

Advisory Details (4)

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

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 pull request 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(20)

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

Patch Availability(30)

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-mlflow-rhel9:17896536062026-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-cuda-rhel9:17896811262026-09-21redhat
redhatrhaii/vllm-spyre-rhel9:17896812012026-09-21redhat
redhatrhaii/vllm-rocm-rhel9:17896811262026-09-21redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
redhatrhaii/model-opt-cuda-rhel9:17896811262026-09-21redhat
redhatrhaii/vllm-cpu-rhel9:17896811282026-09-21redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17882739772026-09-01redhat
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
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
redhatquay/quay-rhel9:17861819812026-08-12redhat
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
redhatansible-automation-platform-27/lightspeed-chatbot-rhel9:17854267342026-08-04redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17856461882026-08-04redhat
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 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

(10)

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 16× in last 7d / 48× 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 301 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 201 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-54058?
CVE-2026-54058 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-54058 published?
The CVE record for CVE-2026-54058 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 August 6, 2026; the record at its source may have been updated since.
Is CVE-2026-54058 actively exploited?
CVE-2026-54058 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-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?
A fix for CVE-2026-54058 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54058 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-54058

Explore →

Is Your Infrastructure Affected by CVE-2026-54058?

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

Book a Demo →Browse All CVEs