CVE-2026-112390: Flaw in python-pillow Pillow Scores 8.2 on CVSS
A newly published high vulnerability in python-pillow Pillow carries a CVSS score of 8.2. Here is what is affected and how to respond.
Key points
- CVE-2026-112390 affects python-pillow Pillow.
- CVSS 8.2 (High).
- No exploitation confirmed yet.
A high security flaw tracked as CVE-2026-112390 has been published in the National Vulnerability Database for python-pillow Pillow, with a CVSS base score of 8.2.
At a glance
- CVE
- CVE-2026-112390
- Product
- python-pillow Pillow
- CVSS
- 8.2 High
- Weakness
- CWE-835
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: Pillow is a Python imaging library. From 7.2.0 until 13.0.0, Pillow can enter an infinite loop while determining the frame count of a MIC image. MicImageFile inherits TIFF frame traversal, but MicImageFile.tell reports the OLE stream index and its seek() resets TIFF frame state, so an embedded TIFF with at least three IFDs never advances. When an application with olefile installed reads n_frames or saves all frames from a crafted MIC file, the non-advancing traversal can hold a worker at full CPU indefinitely. This issue is fixed in version 13.0.0.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Python-Pillow | Pillow | >= 7.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-112390
- 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-112390?
CVE-2026-112390 is a CWE-835 vulnerability in python-pillow Pillow.
How severe is CVE-2026-112390?
It has a CVSS score of 8.2 High.
Is CVE-2026-112390 being exploited?
There is no public confirmation of exploitation at the time of publication.
