CVE-2026-55380

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% 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, secondary
Elevated
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.4%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Pillow is a Python imaging library. Prior to 12.3.0, PIL/GdImageFile.py GdImageFile._open() read image dimensions from the GD 2.x header and stored them in self._size without calling Image._decompression_bomb_check(), allowing a crafted .gd file to trigger excessive C-heap allocation when loaded. This issue is fixed in version 12.3.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
githubMentions a patch (unverified)🟡 PoC Available

`GdImageFile._open()`: image dimensions accepted without `_decompression_bomb_check()` — 1037-byte crafted `.gd` file triggers unchecked 4.3 GB C-heap allocation (24× DecompressionBombError threshold) · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-phj9-mv4w-65pm
github_commit Patch Available

commit f39b0ae6624e (python-pillow/Pillow)

Patch available: python-pillow/Pillow 12.3.0 (contains commit f39b0ae6624e)

https://github.com/python-pillow/Pillow/commit/f39b0ae6624eb2d7c5c5d651d9bb5fdbd96a8675
generic

Pillow/docs/releasenotes/12.3.0.rst at main · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/blob/main/docs/releasenotes/12.3.0.rst

Vendor Advisories for CVE-2026-55380(20)

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

Patch Availability(27)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatrhaii/vllm-cuda-rhel9:17896811262026-09-21redhat
redhatrhaii/vllm-cpu-rhel9:17896811282026-09-21redhat
redhatrhaii/vllm-spyre-rhel9:17896812012026-09-21redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
redhatrhaii/vllm-rocm-rhel9:17896811262026-09-21redhat
redhatrhaii/model-opt-cuda-rhel9:17896811262026-09-21redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17882739772026-09-01redhat
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhaiis/model-opt-cuda-rhel9:17877721572026-08-31redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatrhaiis/vllm-rocm-rhel9:17878848732026-08-31redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhaiis/model-opt-cuda-rhel9:17876011592026-08-25redhat
redhatquay/quay-rhel8:17863950652026-08-11redhat
redhatpython-pillow-0:5.1.1-15.el8_4.22026-08-10redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatquay/quay-rhel8:17859500042026-08-05redhat
redhatpython-pillow-0:12.3.0-1.el9pc2026-08-04redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17856461882026-08-04redhat
redhatpython3.12-pillow-0:12.3.0-1.el9pc2026-08-04redhat
redhatpython3.12-pillow-0:12.3.0-1.el9ap2026-08-04redhat
redhatansible-automation-platform-27/lightspeed-chatbot-rhel9:17854267342026-08-04redhat
redhatpython-pillow-0:5.1.1-20.el8_62026-07-31redhat
redhatpython-pillow-0:5.1.1-20.el8_82026-07-31redhat
redhatquay/quay-rhel8:17852615062026-07-30redhat
redhatpython-pillow-0:5.1.1-22.el8_102026-07-14redhat

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 rangeFix by version rangeDependents
pillow10.0.0-1 ... 9.5.0-1 (38 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pillow10.0.0-1 ... 9.5.0-1 (23 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5 ... 12.3.0-1 (13 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5 ... 12.2.0-1 (8 versions)
  • every version up to 12.3.0-1: fixed in 12.3.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pillow1.0 ... 9.5.0 (106 versions)
  • every version up to 12.3.0: fixed in 12.3.0
—

Weakness Classification(1)

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

Additional Vendor Advisories

(17)

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 7× in last 7d / 35× 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 209 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-55380?
CVE-2026-55380 is a high vulnerability published on July 6, 2026. Pillow is a Python imaging library. Prior to 12.3.0, PIL/GdImageFile.py GdImageFile.open() read image dimensions from the GD 2.x header and stored them in self.size without calling Image.decompressionbomb_check(), allowing a crafted .gd file to trigger excessive C-heap allocation when loaded. This…
When was CVE-2026-55380 disclosed?
CVE-2026-55380 was first published on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55380 actively exploited?
CVE-2026-55380 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55380?
CVE-2026-55380 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55380?
A fix for CVE-2026-55380 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55380 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-55380

Explore →

Is Your Infrastructure Affected by CVE-2026-55380?

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

Book a Demo →Browse All CVEs