CVE-2026-112391
Pillow: PdfParser can recurse without limit in get_value() and linearize_page_tree()
No exploitation reported by the sources we read.
- Published2026-10-19
- Fixed in13.0.0
- WeaknessCWE-835
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Pillow is a Python imaging library. From 5.1.0 until 13.0.0, Pillow's PdfParser.get_value() can recurse without a limit while reading nested PDF objects. The parser follows attacker-controlled arrays and dictionaries when an existing PDF is opened for append. An attacker can provide a deeply nested PDF to an application that saves an image with PDF append enabled. This can raise an uncaught RecursionError or terminate the worker, causing denial of service. This issue is fixed in version 13.0.0.
Timeline
dates in UTC- 2026-10-1921:17CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-112391?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-112391?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 13.0 | ≥ 5.1.0, < 13.0.0 | 13.0.0 | NVD · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
pillow: Pillow: Denial of Service via unbounded recursion in PDF parser
exploit-intelligence/vulnerability-analysis-rhel9 as a component of Exploit Intelligence · lightspeed-core/lightspeed-stack-rhel9 as a component of Lightspeed Core · lightspeed-core/rag-tool-cpu-rhel9 as a component of Lightspeed Core · +81 more
Fix
- Update Python pillow to 13.0.0
- Workaround from the vendor Red Hat Product Security CVE-2026-112391 · 84 products--- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to indepen…
- No fix available, says the vendor Red Hat Product Security CVE-2026-112391 · 84 productsAffected
Advisories and patches
- github.comPatch
- github.comRelease Notes
- github.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CVSS 4.0 vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published
- 2026-10-19
- Last Modified
- 2026-10-23
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-112391?
Is CVE-2026-112391 actively exploited?
What is the CVSS score for CVE-2026-112391?
Running pillow? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.