Advisory record · GHSA-332p-7hrc-92wf

Pillow: Heap buffer overflow in _tiffWriteProc when saving TIFF to BytesIO

CVSS 9.2 CriticalCriticalEPSS 0.010 · 63rd percentile

Critical, because:

  • CVSS score 9.2: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 21 Oct 2026, 21:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pillowPyPI>=2.0.0, <13.0.013.0.0
Identifiers
GHSA-332p-7hrc-92wf · BIT-pillow-2026-112393 · CVE-2026-112393
Weakness (CWE)
CWE-122
Published
21 Oct 2026
Updated
26 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Pillow versions from 2.0.0 up to but not including 13.0.0 are affected. When an image is saved as TIFF to an in-memory target such as io.BytesIO, a bug in the libtiff write callback (_tiffWriteProc) can write past the end of a heap buffer and copy stale heap memory into the output file. An attacker who can supply an image that a service opens and re-saves as TIFF this way can trigger it with default save settings; the source reports a crash and says code execution is not demonstrated. The fixed version is 13.0.0, so upgrade Pillow to 13.0.0 or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.2 Critical 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.010, the 63rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.