Pillow is a Python imaging library. From 8.1.0 until 13.0.0, Pillow's TIFF tile and RGBA decode paths can read beyond row data produced by libtiff. In _decodeTile and the RGBA unpacker path, when Pillow and libtiff interpret duplicated PhotometricInterpretation or BitsPerSample tags differently, Pillow does not verify that the required input row fits inside the row libtiff produced, while the strip path has this validation. Loading pixels from such a crafted TIFF can expose adjacent heap data in output pixels or crash the process. This issue is fixed in version 13.0.0.
CVE-2026-112404
HIGHNVD 8.28.2Trending — 4 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Also known asEUVD-2026-104645 (ENISA EUVD) · GHSA-c6hw-5grf-ff96 (GitHub Security Advisories)Source: ENISA EUVD
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.2
- EG Score
- 8.2HIGHmedium confidence
- EG Risk
- 68EG Risk 68/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity82% × 45%Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 38th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 19, 2026
Last Modified
October 28, 2026
Advisory Details (3)
Auto-updated Oct 19, 2026Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available
13.0.0
Patch available: python-pillow/Pillow 13.0.0
https://github.com/python-pillow/Pillow/releases/tag/13.0.0GitHub commit Patch Available
commit 1d4773e6cea0 (python-pillow/Pillow)
Patch available: python-pillow/Pillow 13.0.0 (contains commit 1d4773e6cea0)
https://github.com/python-pillow/Pillow/commit/1d4773e6cea0c4a2814e6d4cdc099bbcf56da6ceGitHub advisoryMentions a patch (unverified)
OOB read in TiffDecode.c tile and RGBA paths leaks heap memory into pixels · Advisory · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/security/advisories/GHSA-c6hw-5grf-ff96Vendor Advisories for CVE-2026-112404(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:92861Red Hat Product SecurityCritical
Red Hat Security Advisory: Satellite 6.19 security update
- RHSA-2026:92510Red Hat Product SecurityCritical
Red Hat Security Advisory: RHOAI 3.4.6 - Red Hat OpenShift AI
- GHSA-c6hw-5grf-ff96GitHub Security AdvisoriesHigh
Pillow: OOB read in TiffDecode.c tile and RGBA paths leaks heap memory into pixels
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | Pillow @ 13.0.0 (fixes >= 8.1.0, < 13.0.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pillow | 10.0.0 ... 9.5.0 (31 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 24× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-01 07:59 UTCGHSA enrichmentGHSA-c6hw-5grf-ff96 · GitHub severity HIGH
- 2026-11-01 07:59 UTCEG score recompute
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-28 15:25 UTCEG score recompute
- 2026-10-28 15:24 UTCEG score recompute
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-27 15:09 UTCEG score recompute▼ 0.60
- 2026-10-27 15:06 UTCNVD updateCVSS v3 → 8.2
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 14:51 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-20 20:06 UTCEG score recompute
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-19 22:31 UTCEG score recompute
- 2026-10-19 21:33 UTCEG score recomputeFirst assessed: 8.8 HIGH
- 2026-10-19 21:32 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:pillow
Frequently asked(5)
What is CVE-2026-112404?
CVE-2026-112404 is a high-severity vulnerability; its CVE record was published on October 19, 2026. Pillow is a Python imaging library. From 8.1.0 until 13.0.0, Pillow's TIFF tile and RGBA decode paths can read beyond row data produced by libtiff. In _decodeTile and the RGBA unpacker path, when Pillow and libtiff interpret duplicated PhotometricInterpretation or BitsPerSample tags differently,…
When was the CVE record for CVE-2026-112404 published?
The CVE record for CVE-2026-112404 was published on October 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 28, 2026; the record at its source may have been updated since.
Is CVE-2026-112404 actively exploited?
CVE-2026-112404 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112404?
CVE-2026-112404 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-112404?
A fix for CVE-2026-112404 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112404 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-112404
Is Your Infrastructure Affected by CVE-2026-112404?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.