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.8EG
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.8Exploit: None knownExposed: 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 PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

May 9, 2026

Last Modified

July 24, 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(6)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-pil.imagetk (12.1.1-2ubuntu1.2) @ resolute2026-08-23ubuntu
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 rangeFixed inDependents
pillow11.1.0-5, 11.1.0-5+deb13u1, 11.1.0-5+deb13u211.1.0-5+deb13u3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pillow11.1.0-5 ... 12.1.1-2 (7 versions)12.2.0-1—
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.

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 6× in last 7d / 28× 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 184 total refreshes for this CVE.

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

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 July 24, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 95.5% of all 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?
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