python-pillow Pillow Uncontrolled Resource Consumption Flaw (CVE-2026-112400) Rated CVSS 8.7
A newly published high vulnerability in python-pillow Pillow carries a CVSS score of 8.7. Here is what is affected and how to respond.
Key points
- CVE-2026-112400 affects python-pillow Pillow.
- CVSS 8.7 (High).
- No exploitation confirmed yet.
python-pillow Pillow is affected by CVE-2026-112400, a uncontrolled resource consumption that the National Vulnerability Database rates 8.7 out of 10.
At a glance
- CVE
- CVE-2026-112400
- Product
- python-pillow Pillow
- CVSS
- 8.7 High
- Weakness
- uncontrolled resource consumption
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: Pillow is a Python imaging library. From 9.2.0 until 13.0.0, Pillow can retain a rejected GIF frame size after a decompression-bomb exception. In GifImageFile._seek, a crafted GIF can leave rejected dimensions stored after Image.DecompressionBombError; if an application catches that exception and continues processing the same image object, later seek or load operations allocate according to those dimensions and can exhaust memory, denying service. This issue is fixed in version 13.0.0.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Python-Pillow | Pillow | >= 9.2.0, < 13.0.0 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-112400
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-112400?
CVE-2026-112400 is a uncontrolled resource consumption vulnerability in python-pillow Pillow.
How severe is CVE-2026-112400?
It has a CVSS score of 8.7 High.
Is CVE-2026-112400 being exploited?
There is no public confirmation of exploitation at the time of publication.
