Pillow: Memory disclosure and segfault in libtiff encoder via crafted TIFF tags
Affects Pillow 12.3.0 and earlier in applications that re-save compressed uploaded images as TIFF. Fixed in 13.0.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 13.0.0
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Pillow, a Python imaging library, has a flaw in its libtiff TIFF encoder that can read and leak process memory or crash the program when it saves crafted image metadata. An attacker can reach it remotely, without logging in, by getting an application to re-save compressed TIFF images or convert EXIF-carrying images into compressed TIFF output.
Read the original description
Pillow is a Python imaging library. In versions through 12.3.0, the libtiff TIFF encoder can pass arguments to TIFFSetField() that do not match libtiff’s definition of the corresponding tag. When an application saves attacker-controlled image metadata through this encoder, crafted tag values can cause invalid memory reads, copying process memory into the encoded output or crashing the process. Applications that return the encoded output to an attacker can disclose that memory. The issue is reachable when re-saving compressed TIFF images and through certain conversions that preserve EXIF metadata into compressed TIFF output. This vulnerability is fixed in version 13.0.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 13.0.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- python-pillow Pillow
fixed in 13.0.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112902
Is CVE-2026-112902 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted TIFF file with unrecognised tags makes Pillow copy an attacker-chosen amount of its own process memory into the TIFF output it writes. The same input can instead crash the process.Source: github.com
Which versions are affected by CVE-2026-112902?
Pillow: before 13.0.0.Source: cve.now feed data
Am I affected, and how do I check?
Pillow 12.3.0 and earlier are affected, and only when an application re-saves images as TIFF. Compressed source images are routed through the libtiff writer automatically. To check an installed version, run python -c 'import PIL; print(PIL.__version__)' or python -m pip show Pillow.Source: github.com
How do I fix CVE-2026-112902?
Upgrade Pillow to 13.0.0 or later. The advisory lists no workaround.Source: github.com