CVE-2026-42309

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% 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
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

Pillow is a Python imaging library. From version 11.2.1 to before version 12.2.0, passing nested lists as coordinates to APIs that accept coordinates such as ImagePath.Path, ImageDraw.ImageDraw.polygon and ImageDraw.ImageDraw.line could cause a heap buffer overflow, as nested lists were recursively unpacked beyond the allocated buffer. Coordinate lists are now validated to contain exactly two numeric coordinates. This issue has been patched in version 12.2.0.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
3.2%
KEV
Not listed

Published

May 9, 2026

Last Modified

May 12, 2026

Advisory Details (2)

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

Heap buffer overflow with nested list coordinates · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-5xmw-vc9v-4wf2
generic

Release 12.2.0 · python-pillow/Pillow · GitHub

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

Vendor Advisories for CVE-2026-42309(3)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-pil.imagetk (12.1.1-2ubuntu1.2) @ resolute2026-06-28ubuntu
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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pillow11.2.1, 11.3.0, 12.0.0, 12.1.0, 12.1.112.2.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 9× in last 7d / 42× 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 118 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42309?
CVE-2026-42309 is a medium vulnerability published on May 9, 2026. Pillow is a Python imaging library. From version 11.2.1 to before version 12.2.0, passing nested lists as coordinates to APIs that accept coordinates such as ImagePath.Path, ImageDraw.ImageDraw.polygon and ImageDraw.ImageDraw.line could cause a heap buffer overflow, as nested lists were recursively…
When was CVE-2026-42309 disclosed?
CVE-2026-42309 was first published in the National Vulnerability Database on May 9, 2026, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42309 actively exploited?
CVE-2026-42309 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42309?
CVE-2026-42309 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-42309?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42309, 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-42309

Explore →

Is Your Infrastructure Affected by CVE-2026-42309?

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

Start Free Scan →Browse All CVEs