Quick answers
- Is CVE-2026-112394 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112394 being exploited in the wild.
- How severe is CVE-2026-112394?
- Medium severity, with a CVSS score of 4, published 19 October 2026.
- Which products and versions are affected?
- pillow (PyPI) <= 12.3.0, ECOSYSTEM:introduced=0,fixed=13.0.0; Python Pillow Pillow before 13.0.0.
- Is there a fix for CVE-2026-112394?
- Yes. pillow (PyPI): upgrade to 13.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112394 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-112394?
- Check whether you run pillow (PyPI) or Python Pillow Pillow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- pillow (PyPI): upgrade to 13.0.0 or later
pip install "pillow>=13.0.0"
Technical details
The ImagingRawDecode function calculates packed-pixel row size incorrectly for P;2L and P;4L raw modes, while unpackers read separately padded bit planes. An attacker can supply a buffer and image dimensions whose declared size is smaller than the unpacker's actual memory footprint, causing out-of-bounds reads. The vulnerability allows information disclosure of heap data or denial of service via crash.
Affected products
- Python Pillow Pillow before 13.0.0
Identifiers
- CVE-2026-112394
- BIT-PILLOW-2026-112394
- GHSA-4558-3h8r-v8xp
- PYSEC-2026-4327
Timeline
- 2026-10-19: disclosed
- 2026-10-16: patched