Skip to main content
VulnerabilityPublished

CVE-2026-96638: Pillow · BMP RLE decoder memory-amplification DoS via unbounded delta escape / absolute mode

Affects pillowSource GCVE Database

0
Compare
Authoritative record:CVE-2026-96638· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 13.0.0 when convenient.

Data as of 29 Oct 2026, 13:06 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.5
Patch
Available – fixed in 13.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Oct 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 29 Oct 2026.

What to do

Upgrade pillow to 13.0.0.

Affected software

ProductAffectedFixed in
Bitnamipillowpkg:bitnami/pillowOther threatsAffected
  • >=9.1.0 <13.0.0
Fixed in
  • 13.0.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 13.0.0 or later, where this vulnerability is fixed. The vendor has released an official patch (commit e7794835e323ff2691d9b3a974cade1a44301b9a) addressing this issue. No other mitigations are indicated.

Description

A vulnerability in the Pillow Python imaging library versions 9.1.0 through 12.x allows crafted BMP RLE images to cause excessive memory allocation during decoding. This memory amplification can lead to denial of service by exhausting system memory. The issue is fixed in version 13.0.0.

References

Community reviews

Loading reviews…