CVE-2026-40192

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 51% 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: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Pillow is a Python imaging library. Versions 10.3.0 through 12.1.1 did not limit the amount of GZIP-compressed data read when decoding a FITS image, making them vulnerable to decompression bomb attacks. A specially crafted FITS file could cause unbounded memory consumption, leading to denial of service (OOM crash or severe performance degradation). If users are unable to immediately upgrade, they should only open specific image formats, excluding FITS, as a workaround.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

April 15, 2026

Last Modified

August 21, 2026

Advisory Details (4)

Auto-updated Jun 11, 2026
Patch available. Sources: github_commit, github_pr, github.
generic

12.2.0 (2026-04-01) - Pillow (PIL Fork) 12.2.0 documentation

https://pillow.readthedocs.io/en/stable/releasenotes/12.2.0.html#prevent-fits-decompression-bomb
github Patch Available

FITS GZIP decompression bomb in Pillow < 12.2.0 · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-whj4-6x5x-4v2j
github_pr Patch Available

Only read as much data from gzip-decompressed data as necessary

Patch available: python-pillow/Pillow 12.2.0 (PR #9521 merged 2026-03-31)

https://github.com/python-pillow/Pillow/pull/9521
github_commit Patch Available

commit 3cb854e8b2ba (python-pillow/Pillow)

Patch available: python-pillow/Pillow 12.2.0 (contains commit 3cb854e8b2ba)

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

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaii/vllm-spyre-rhel9:17871518402026-08-20redhat
redhatrhoai/odh-trustyai-nemo-guardrails-server-rhel9:17824716062026-07-09redhat
redhatpython3.12-pillow-0:12.2.0-1.el9pc2026-07-01redhat
redhatpython-pillow-0:12.2.0-1.el9pc2026-07-01redhat
redhatrhoai/odh-caikit-tgis-serving-rhel9:17803881332026-06-10redhat
redhatpython3.12-pillow-0:12.2.0-1.el9ap2026-06-09redhat
redhatquay/quay-rhel8:17808913952026-06-09redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17801027322026-06-09redhat
redhatquay/quay-rhel8:17798114732026-06-04redhat
redhatquay/quay-rhel8:17798222612026-06-03redhat
redhatquay/quay-rhel8:17798114122026-06-02redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17786777222026-05-20redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
redhatrhelai3/disk-image-cuda-rhel9:17786906392026-05-14redhat
redhatrhelai3/bootc-rocm-rhel9:17786661242026-05-14redhat
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatrhaiis/model-opt-cuda-rhel9:17782445592026-05-11redhat
redhatrhaiis/vllm-cuda-rhel9:17782746662026-05-11redhat
redhatrhaiis/vllm-rocm-rhel9:17782445312026-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+deb13u111.1.0-5+deb13u2
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(3)

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

Additional Vendor Advisories

(4)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-40192?
CVE-2026-40192 is a high vulnerability published on April 15, 2026. Pillow is a Python imaging library. Versions 10.3.0 through 12.1.1 did not limit the amount of GZIP-compressed data read when decoding a FITS image, making them vulnerable to decompression bomb attacks. A specially crafted FITS file could cause unbounded memory consumption, leading to denial of…
When was CVE-2026-40192 disclosed?
CVE-2026-40192 was first published in the National Vulnerability Database on April 15, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40192 actively exploited?
CVE-2026-40192 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.5% of all scored CVEs.
What is the CVSS score of CVE-2026-40192?
CVE-2026-40192 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-40192?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40192, 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-40192

Explore →

Is Your Infrastructure Affected by CVE-2026-40192?

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