CVE-2026-112396

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.9 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-10-21) is not newer than that change (2026-10-26), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-104632 (ENISA EUVD) · GHSA-4rr5-89j8-mwwm (GitHub Security Advisories) · PYSEC-2026-4328 (OSV.dev)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in ImagingLibTiffEncode; the error path then frees the output buffer without closing or clearing the TIFF handle, and later cleanup flushes through the write callback into freed memory, which can crash the process and may enable code execution. This issue is fixed in version 13.0.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.7%
EPSS %ILE
53rd
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 26, 2026

Advisory Details (3)

Auto-updated Oct 19, 2026
🔬 Proof of concept available. Patch 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.0
GitHub commit Patch Available

commit dc95da202078 (python-pillow/Pillow)

Patch available: python-pillow/Pillow 13.0.0 (contains commit dc95da202078)

https://github.com/python-pillow/Pillow/commit/dc95da20207827a062cfbf551ee9f6031465a8bb
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Heap use-after-free when encoding TIFF to an in-memory buffer · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-4rr5-89j8-mwwm

Vendor Advisories for CVE-2026-112396(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhaii/model-opt-cuda-rhel9:17934443392026-11-03redhat
redhatrhaii/vllm-gaudi-rhel9:17934445102026-11-03redhat
redhatrhaii/vllm-cpu-rhel9:17934445542026-11-03redhat
redhatrhaii/vllm-rocm-rhel9:17934444562026-11-03redhat
redhatrhaii/vllm-spyre-rhel9:17934444092026-11-03redhat
redhatrhaii/vllm-cuda-rhel9:17934446002026-11-03redhat
pippillow @ 13.0.0 (fixes >= 11.3.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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pillow10.0.0-1 ... 9.5.0-1 (24 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5 ... 13.0.0-1 (14 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5 ... 13.0.0-1 (10 versions)
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.3.0 ... 12.3.0 (6 versions)
  • 11.3.0 up to 13.0.0: fixed in 13.0.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 30× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-10 08:38 UTCEchelonGraph re-scored
  5. 2026-11-10 08:38 UTCVendor advisory
  6. 2026-11-10 08:38 UTCGHSA enrichmentGHSA-4rr5-89j8-mwwm · GitHub severity MODERATE · GitHub CVSS 5.9
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-11-03 02:52 UTCEchelonGraph re-scored
  15. 2026-11-03 02:52 UTCGHSA enrichmentGHSA-4rr5-89j8-mwwm · GitHub severity MODERATE · GitHub CVSS 5.9
  16. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-4rr5-89j8-mwwm · GitHub severity MODERATE · GitHub CVSS 5.9
  19. 2026-11-01 07:59 UTCEchelonGraph re-scored
  20. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-26 21:06 UTCEchelonGraph re-scored▲ 1.60
Show 14 more
  1. 2026-10-26 21:05 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  2. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-10-25 14:51 UTCEchelonGraph re-scored
  5. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-20 17:31 UTCEchelonGraph re-scored
  10. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  11. 2026-10-20 16:19 UTCEchelonGraph re-scored
  12. 2026-10-19 22:35 UTCEchelonGraph re-scored
  13. 2026-10-19 21:24 UTCEchelonGraph re-scoredFirst assessed: 5.9 MEDIUM
  14. 2026-10-19 21:22 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-112396?
CVE-2026-112396 is a high-severity vulnerability; its CVE record was published on October 19, 2026. Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in…
When was the CVE record for CVE-2026-112396 published?
The CVE record for CVE-2026-112396 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 26, 2026; the record at its source may have been updated since.
Is CVE-2026-112396 actively exploited?
CVE-2026-112396 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112396?
CVE-2026-112396 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-112396?
A fix for CVE-2026-112396 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112396 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-112396

Explore →

Is Your Infrastructure Affected by CVE-2026-112396?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs