CVE-2026-42311

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.1% (4th 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 — 3 sources updated this week

Also known asEUVD-2026-28903 (ENISA EUVD)Source: ENISA EUVD

7.8EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Pillow is a Python imaging library. From version 10.3.0 to before version 12.2.0, processing a malicious PSD file could lead to memory corruption, potentially resulting in a crash or arbitrary code execution. This issue has been patched in version 12.2.0.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
50
EG Risk 50/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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.1%
EPSS %ILE
4th
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS. 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: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: 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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

May 9, 2026

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated May 9, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

OOB Write with Invalid PSD Tile Extents (Integer Overflow) · Advisory · python-pillow/Pillow · GitHub

Affected: 12.2.0

https://github.com/python-pillow/Pillow/security/advisories/GHSA-pwv6-vv43-88gr
Web page

Release 12.2.0 · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/releases/tag/12.2.0
Web page

Avoid overflow by not adding extents together by hugovk · Pull Request #9520 · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/pull/9520
Web page

Avoid overflow by not adding extents together (#9520) · python-pillow/Pillow@58f9a1d · GitHub

https://github.com/python-pillow/Pillow/commit/58f9a1d166dcb0c274807d4423522d205b0c35ea

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-pil.imagetk (11.3.0-1ubuntu1.3) @ questing2026-10-24ubuntu
redhatrhaii/vllm-spyre-rhel9:17900761412026-09-23redhat
redhatrhaii/vllm-spyre-rhel9:17896812012026-09-21redhat
redhatrhaiis/model-opt-cuda-rhel9:17877721572026-08-31redhat
redhatrhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:17866132092026-08-27redhat
redhatrhaii/vllm-spyre-rhel9:17871518402026-08-20redhat
redhatrhaiis/model-opt-cuda-rhel9:17782445592026-05-11redhat
redhatrhaiis/vllm-rocm-rhel9:17782445312026-05-11redhat
redhatrhaiis/vllm-cuda-rhel9:17782746662026-05-11redhat

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

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5, 11.1.0-5+deb13u1, 11.1.0-5+deb13u2
  • every version up to 11.1.0-5+deb13u3: fixed in 11.1.0-5+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5 ... 12.1.1-2 (7 versions)
  • every version up to 12.2.0-1: fixed in 12.2.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pillow10.3.0 ... 12.1.1 (9 versions)
  • 10.3.0 up to 12.2.0: fixed in 12.2.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 9× in last 7d / 38× 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 231 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 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-42311?
CVE-2026-42311 is a high-severity vulnerability; its CVE record was published on May 9, 2026. Pillow is a Python imaging library. From version 10.3.0 to before version 12.2.0, processing a malicious PSD file could lead to memory corruption, potentially resulting in a crash or arbitrary code execution. This issue has been patched in version 12.2.0.
When was the CVE record for CVE-2026-42311 published?
The CVE record for CVE-2026-42311 was published on May 9, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-42311 actively exploited?
CVE-2026-42311 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42311?
CVE-2026-42311 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-42311?
A fix for CVE-2026-42311 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42311 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-42311

Explore →

Is Your Infrastructure Affected by CVE-2026-42311?

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