CVE-2026-25990

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% 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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Pillow is a Python imaging library. From 10.3.0 to before 12.1.1, an out-of-bounds write may be triggered when loading a specially crafted PSD image. This vulnerability is fixed in 12.1.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

Published

February 11, 2026

Last Modified

September 16, 2026

Advisory Details (3)

Auto-updated Apr 30, 2026
Patch available. Sources: github.
generic

oss-security - Pillow 12.1.1 released with fix for CVE-2026-25990

http://www.openwall.com/lists/oss-security/2026/02/12/1
githubMentions a patch (unverified)

Out-of-bounds write when loading PSD images · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-cfh3-3jmp-rvhc
generic

Fix OOB Write with invalid tile extents (#9427) · python-pillow/Pillow@9000313 · GitHub

https://github.com/python-pillow/Pillow/commit/9000313cc5d4a31bdcdd6d7f0781101abab553aa

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-pil.imagetk (11.3.0-1ubuntu1.1) @ questing2026-09-16ubuntu
redhatrhoai/odh-vllm-rocm-rhel9:17839988572026-07-21redhat
redhatpython3.12-pillow-0:12.1.1-1.el9pc2026-06-23redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17786001872026-05-20redhat
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatpython-pillow-0:12.1.1-1.el9pc2026-05-07redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17763192752026-04-23redhat
redhatquay/quay-rhel9:17751692262026-04-03redhat
redhatquay/quay-rhel8:17751692192026-04-03redhat
redhatquay/quay-rhel9:17750694912026-04-02redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17744170222026-04-01redhat
redhatpython3.12-pillow-0:12.1.1-1.el9ap2026-03-31redhat
redhatansible-automation-platform-25/lightspeed-chatbot-rhel8:17744146992026-03-31redhat
redhatquay/quay-rhel8:17739710772026-03-24redhat
redhatquay/quay-rhel8:17739363232026-03-19redhat
redhatquay/quay-rhel8:17737719622026-03-18redhat
redhatrhaiis/model-opt-cuda-rhel9:17727138302026-03-09redhat
redhatrhaiis/vllm-cuda-rhel9:17721605932026-02-27redhat
redhatrhaiis/vllm-rocm-rhel9:17721606252026-02-27redhat

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
  • every version up to 11.1.0-5+deb13u1: fixed in 11.1.0-5+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5, 11.2.1-1, 11.3.0-1, 12.0.0-1, 12.1.0-1
  • every version up to 12.1.1-1: fixed in 12.1.1-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pillow10.3.0 ... 12.1.0 (8 versions)
  • 10.3.0 up to 12.1.1: fixed in 12.1.1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 8× in last 7d / 25× 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 223 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-25990?
CVE-2026-25990 is a high vulnerability published on February 11, 2026. Pillow is a Python imaging library. From 10.3.0 to before 12.1.1, an out-of-bounds write may be triggered when loading a specially crafted PSD image. This vulnerability is fixed in 12.1.1.
When was CVE-2026-25990 disclosed?
CVE-2026-25990 was first published on February 11, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25990 actively exploited?
CVE-2026-25990 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25990?
CVE-2026-25990 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-25990?
A fix for CVE-2026-25990 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-25990 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-25990

Explore →

Is Your Infrastructure Affected by CVE-2026-25990?

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