CVE-2026-42311

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 95% 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
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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.8(medium)
EG Risk
50(Track)
EG Risk 50/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
Severity78% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
4.6%
KEV
Not listed

Published

May 9, 2026

Last Modified

May 14, 2026

Advisory Details (4)

Auto-updated May 9, 2026
Patch available. Sources: github.
github Patch Available

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
generic

Release 12.2.0 · python-pillow/Pillow · GitHub

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

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

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

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

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

Vendor Advisories for CVE-2026-42311(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-pil.imagetk (12.1.1-2ubuntu1.2) @ resolute2026-06-28ubuntu

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pillow10.3.0 ... 12.1.1 (9 versions)12.2.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42311?
CVE-2026-42311 is a high vulnerability 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 CVE-2026-42311 disclosed?
CVE-2026-42311 was first published in the National Vulnerability Database on May 9, 2026, with the most recent update on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42311 actively exploited?
CVE-2026-42311 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42311, 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-42311

Explore →

Is Your Infrastructure Affected by CVE-2026-42311?

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

Start Free Scan →Browse All CVEs