Skip to main content
VulnerabilityPublished

CVE-2026-55380: Pillow · Excessive Memory Allocation

Affects PillowSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 12.3.0 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 12.3.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Pillow and pillow to 12.3.0.

Affected software

ProductAffectedFixed in
python-pillowPillowAffected
  • <12.3.0
Fixed in
  • 12.3.0
PyPIpillowpkg:pypi/pillowOther threatsAffected
  • <12.3.0
Fixed in
  • 12.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Pillow to version 12.3.0 or later, where this vulnerability is fixed. Patch status is confirmed by the version fix information. No other mitigation is indicated.

Description

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.

References

Community reviews

Loading reviews…