Quick answers
- Is CVE-2026-96643 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96643 being exploited in the wild.
- How severe is CVE-2026-96643?
- High severity, with a CVSS score of 4, published 21 October 2026.
- Which products and versions are affected?
- Pillow 11.0.0 to 12.x (before 13.0.0); pillow (PyPI) >= 11.0.0, < 13.0.0, ECOSYSTEM:introduced=11.0.0,fixed=13.0.0.
- Is there a fix for CVE-2026-96643?
- 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-96643 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96643?
- Check whether you run Pillow or pillow (PyPI) 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 vulnerability exists in Exif.load() (src/PIL/Image.py) which repeatedly slices EXIF data when it begins with the six-byte Exif header. PNG eXIf chunks are uncapped, allowing a file with repeated headers to trigger quadratic CPU work as each iteration creates a new shrinking copy. The flaw is reachable via Image.getexif(), Image._getexif(), and ImageOps.exif_transpose(), making it exploitable in common photo-upload workflows.
Affected products
- Pillow Pillow 11.0.0 to 12.x (before 13.0.0)
Identifiers
- CVE-2026-96643
- BIT-PILLOW-2026-96643
- GHSA-g4qv-2jxx-769h
- PYSEC-2026-4342
Timeline
- 2026-10-21: disclosed
- 2026-09-28: patched