CVE
CVE-2026-112393
- First Reported
- Oct 23, 2026
- Latest Reported
- Oct 23, 2026
CVE Enrichment
- CVSS
- 9.2 CRITICAL
- EPSS
- 0.53%
- EPSS Percentile
- 43.89%
- CISA KEV
- Not listed
Description
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.
Technical Details
- CVSS Version
- 4.0
- CNA / NVD Source
- [email protected]
- Published
- 20-Oct-2026 04:17
- Last Modified
- 21-Oct-2026 02:48
- EPSS Date
- 2026-10-23
- CWE
- CWE-122
CVSS Vector
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 /
E:X /
CR:X /
IR:X /
AR:X /
MAV:X /
MAC:X /
MAT:X /
MPR:X /
MUI:X /
MVC:X /
MVI:X /
MVA:X /
MSC:X /
MSI:X /
MSA:X /
S:X /
AU:X /
R:X /
V:X /
RE:X /
U:X
References
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (1)
- A third flaw, CVE-2026-112393, has been in Pillow since 2013. It overflows a memory buffer when a program saves a compressed TIFF image to memory rather than to a file on disk, the common pattern for a service that Pillow Flaw Enables Command Execution via an Attacker-Controlled Filename
CVE (2)
MITRE ATT&CK (1)
Products (3)
Tools (1)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
