Quick answers
- Is CVE-2026-112893 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112893 being exploited in the wild.
- How severe is CVE-2026-112893?
- High severity, with a CVSS score of 4, published 19 October 2026.
- Which products and versions are affected?
- pillow (PyPI) >= 10.0.0, < 13.0.0, ECOSYSTEM:introduced=10.0.0,fixed=13.0.0; Python Pillow Project Pillow 10.0.0 through 12.x.
- Is there a fix for CVE-2026-112893?
- 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-112893 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112893?
- Check whether you run pillow (PyPI) or Python Pillow Project 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
A use-after-free vulnerability exists in the FreeType glyph rendering code when a stroker is active. If FT_Load_Glyph fails, the cleanup code attempts to free an uninitialized or stale glyph pointer via FT_Done_Glyph, causing heap corruption. An attacker can trigger the glyph-load failure path by supplying a crafted font file to any application that renders text with nonzero stroke width. The fix initializes the glyph pointer to NULL and adds proper cleanup guards.
Affected products
- Python Pillow Project Pillow 10.0.0 through 12.x
Identifiers
- CVE-2026-112893
- GHSA-j4m9-6w36-pw47
Timeline
- 2026-10-19: disclosed
- 2026-10-16: patched: Fix released in version 13.0.0