CVE-2026-42310

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.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

Pillow is a Python imaging library. From version 4.2.0 to before version 12.2.0, an attacker can supply a malicious PDF that causes the process to hang indefinitely, consuming 100% CPU and making the application unresponsive. This issue has been patched in version 12.2.0.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
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

PDF Parsing Trailer Infinite Loop (DoS) · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-r73j-pqj5-w3x7
generic

Release 12.2.0 · python-pillow/Pillow · GitHub

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

Raise an error if the trailer chain loops back on itself by hugovk · Pull Request #9519 · python-pillow/Pillow · GitHub

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

Raise an error if the trailer chain loops back on itself (#9519) · python-pillow/Pillow@3bf614e · GitHub

https://github.com/python-pillow/Pillow/commit/3bf614e4b8615d0ce1d5039efaf6db447fe7c468

Vendor Advisories for CVE-2026-42310(4)

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 (11.3.0-1ubuntu1.3) @ questing2026-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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pillow10.0.0-1 ... 9.5.0-1 (38 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pillow10.0.0-1 ... 9.5.0-1 (23 versions)——
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.0.0 ... 9.5.0 (51 versions)12.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 6× in last 7d / 55× 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 169 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42310?
CVE-2026-42310 is a medium vulnerability published on May 9, 2026. Pillow is a Python imaging library. From version 4.2.0 to before version 12.2.0, an attacker can supply a malicious PDF that causes the process to hang indefinitely, consuming 100% CPU and making the application unresponsive. This issue has been patched in version 12.2.0.
When was CVE-2026-42310 disclosed?
CVE-2026-42310 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-42310 actively exploited?
CVE-2026-42310 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 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-42310?
CVE-2026-42310 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-42310?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42310, 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-42310

Explore →

Is Your Infrastructure Affected by CVE-2026-42310?

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

Start Free Scan →Browse All CVEs