CVE-2026-112393
Pillow: Heap buffer overflow in _tiffWriteProc when saving TIFF to BytesIO
No known exploitation. EPSS puts it in the 64th percentile. A vendor fix is available.
No public exploit knownFixVendor fixNo build named by the sources
No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.
What to do
The vendor has published a fix. Version details are below where the sources state them.
- python-pillow PillowAffected: >= 2.0.0, < 13.0.0Upgrade to: not statedStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check if your website, app, or internal tools use the Pillow Python library to process or convert TIFF images in memory (e.g. via BytesIO) rather than directly to/from disk files.
- If you don't know, ask your developer or software vendor whether Pillow is used and how TIFF files are handled.
- Upgrade Pillow to version 13.0.0 or later, where this issue is fixed.
- If you can't upgrade right away, avoid accepting TIFF image uploads from untrusted users until you do.
pip install --upgrade pillow>=13.0.0What it is
From the CVE record
Pillow is a Python imaging library. From 2.0.0 until 13.0.0, Pillow has a heap buffer overflow and stale-heap disclosure in _tiffWriteProc when saving compressed TIFF data through libtiff to a target without a usable fileno(), such as BytesIO. The callback sizes its allocation from the prior buffer size instead of the current write position, allowing an attacker-controlled out-of-line TIFF tag or retained ICC profile to be copied beyond the allocation after libtiff seeks forward. This overflow can crash the process and may allow code execution. Independently, unwritten alignment gaps in compressed TIFF output larger than 64 KiB can disclose stale heap bytes without a crafted tag. File paths and targets with real file descriptors are unaffected. This issue is fixed in version 13.0.0.
In plain language
Written by AI from the recordThis is a flaw in Pillow, a Python library many apps use to process images, that could crash a program or leak stray memory data when saving certain TIFF images in memory — it's fixed in version 13.0.0, but there's no sign anyone is exploiting it, so there's no need to panic.
Heap buffer overflow (CWE-122) in Pillow's _tiffWriteProc callback when writing compressed TIFF data to a file-like object without a real file descriptor (e.g. BytesIO); a crafted out-of-line TIFF tag or ICC profile can cause an under-sized allocation to be overrun during a libtiff forward seek, risking a crash, heap data disclosure, or potentially code execution.
If you're affected
- Application crash/denial of service
- Stale memory data leak
- Possible code execution
- Operational disruption during image processing
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
1.0% chance of exploitation activity in the next 30 days, which ranks it in the 64th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
7 events over 7 days, from the signal feeds we watch.
- Patch availablerecord updated
- Record updated
- Publishedweakness classified, att&ck mapped, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored 9.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Privilege EscalationT1068Exploitation for Privilege Escalationhigh confidence
Sources
References in the record
In the news
- ⚡ Weekly Recap: This2Shell, That2Shell, Everything's an RCE? Rogue AI, Supply Chain Chaos and More
- Critical Flaw in Python’s Popular Pillow Image Library Allows Code Execution via a Crafted Image
- Three Critical Pillow CVEs: RCE and Heap Overflows in Python’s Imaging Library – CVE-2026-112900 CVE-2026-112393 CVE-2026-112403
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Pillow, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI