Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.8

Docker images with Pillow may crash or run code

published 2 days ago
Summary

The Python image library Pillow, included in several hardened Docker images, can mishandle certain multi‑frame picture files and write data outside its memory area. This can cause the program to stop working or, in rare cases, let an attacker run code. Update Pillow to version 13.0.0 or later in those Docker images to fix the issue.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Debian:13 docker hardened images datascience-notebook All versions
Docker Hardened Images:Debian:13 docker hardened images litellm All versions
Docker Hardened Images:Debian:13 docker hardened images mlflow All versions
Docker Hardened Images:Debian:13 docker hardened images netbox All versions
Docker Hardened Images:Debian:13 docker hardened images pytorch-2.11-cuda12.8-python3.11 All versions
Docker Hardened Images:Debian:13 docker hardened images pytorch-2.11-cuda12.9-python3.12 All versions
Docker Hardened Images:Debian:13 docker hardened images pytorch-2.11-cuda13.0-python3.11 All versions
Docker Hardened Images:Debian:13 docker hardened images pytorch-2.13-cuda12.6-python3.11 All versions
Docker Hardened Images:Debian:13 docker hardened images pytorch-2.13-cuda13.0-python3.12 All versions
Docker Hardened Images:Debian:13 docker hardened images pytorch-2.7-cuda12.8-python3.12 All versions
Docker Hardened Images:Debian:13 docker hardened images pytorch-2.9-cuda12.9-python3.12 All versions
Docker Hardened Images:Debian:13 docker hardened images superset All versions
Original advisory text
Pillow is a Python imaging library. From 11.0.0 until 13.0.0, multi-frame loaders can retain an ImagingCore allocation…
Pillow is a Python imaging library. From 11.0.0 until 13.0.0, multi-frame loaders can retain an ImagingCore allocation created for a narrow frame mode while a later frame of the same dimensions changes the logical mode and decoder tiles to wider RGB or CMYK data. ImageFile.load_prepare() reuses the stale native storage because _im is non-null without verifying that its mode and size still match. Crafted PSD, MPO, DCX, or MIC frame transitions can then write wider pixels into the narrow allocation, causing native out-of-bounds writes and crashes. The MPO path can also cause a native over-read and, in demonstrated runtime-specific profiles, command execution. This issue is fixed in version 13.0.0.
Fix within
Internet-facing 3 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker full control (estimated)
Severity
9.8 Critical
Timeline
Published20 Nov 2026
Updated20 Nov 2026
First seen20 Nov 2026
Sources
Track software like this
Free during beta