Skip to main content
VulnerabilityPublished

CVE-2026-96639: Pillow multi-frame loaders can reuse stale native image storage after mode transitions

Affects pillowSource GCVE Database

0
Compare
Authoritative record:CVE-2026-96639· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical : upgrade to 13.0.0 as a priority.

Data as of 29 Oct 2026, 13:06 UTC

CVSS 3.1 base score
9.8Critical
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.19.8
Patch
Available – fixed in 13.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
  • >=11.0.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. Applying this official fix eliminates the risk associated with stale native image storage reuse after mode transitions in multi-frame loaders.

Description

Pillow versions from 11.0.0 up to but not including 13.0.0 contain a vulnerability in multi-frame image loaders where stale native image storage is reused after mode transitions. This can cause out-of-bounds writes and crashes, and in some cases, native over-reads leading to potential command execution. The issue is fixed in version 13.0.0.

References

Community reviews

Loading reviews…