Skip to main content
CVE-2026-59203VulnerabilityPublished Updated

From 12.0.0 through 12.2.0, Pillow's EPS parser in PIL/EpsImagePlugin.py accepts a negative byte count in the

Affects pillowSource GCVE Database

0
Compare
Authoritative record:CVE-2026-59203· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 12.3.0 : update pillow when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 34% 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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 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 4 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.04 LTSpillowpkg:deb/ubuntu/pillow?arch=source&distro=resoluteOther threatsAffected
  • 11.3.0-1ubuntu1 – 12.1.1-2ubuntu1.4
9 affected builds
Fixed in–

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 issue is fixed. No other mitigations are indicated.

Description

Pillow versions from 12.0.0 through 12.2.0 contain a vulnerability in the EPS parser (PIL/EpsImagePlugin.py) where a negative byte count in the %%BeginBinary directive allows an infinite loop during image parsing. This flaw is fixed in version 12.3.0.

References

Community reviews

Loading reviews…