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

Why it is Amber

• CVSS 9.2 critical
• Public exploit or proof of concept referenced
• Remotely exploitable without logging in
• On your watchlist: PyPI

Affected packages

References

• https://github.com/advisories/GHSA-332p-7hrc-92wf
• https://github.com/python-pillow/Pillow/security/advisories/GHSA-332p-7hrc-92wf
• https://nvd.nist.gov/vuln/detail/CVE-2026-112393
• https://github.com/python-pillow/Pillow/commit/11582e5ffbdceb973d5ee593f3105af5a9852b40
• https://github.com/python-pillow/Pillow/releases/tag/13.0.0
• https://github.com/advisories/GHSA-332p-7hrc-92wf

Original 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.