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 65% 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
Trending — 3 sources updated this weekElevated
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%CVSS: 7.5Exploit: Elevated riskExposed: 0

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.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
35%
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.
github Patch Available🟡 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(17)

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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatquay/quay-rhel8:17863950652026-08-11redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatpython-pillow-0:5.1.1-15.el8_4.22026-08-10redhat
redhatquay/quay-rhel8:17859500042026-08-05redhat
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
redhatpython-pillow-0:12.3.0-1.el9pc2026-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 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 ... 12.3.0-1 (13 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pillow11.1.0-5 ... 12.2.0-1 (8 versions)12.3.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pillow1.0 ... 9.5.0 (106 versions)12.3.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 109× 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 149 total refreshes for this CVE.

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

Related CVEs(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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 65.4% of all scored CVEs.
What is the CVSS score of CVE-2026-55380?
CVE-2026-55380 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55380?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55380, 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-55380

Explore →

Is Your Infrastructure Affected by CVE-2026-55380?

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

Start Free Scan →Browse All CVEs