Security Resilience

CVE-2026-112892

Python Pillow 4.1.0 – 13.0.0

Published
19 October 2026
Modified
27 October 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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
EPSS Score 0.0050 43th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-112892 is a high-severity Data Amplification (CWE-409) vulnerability in Python Pillow. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-6 (Resource Availability) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Pillow is a Python imaging library. From 4.1.0 until 13.0.0, Pillow's MSP RLE decoder can expand a small file into an unbounded in-memory buffer. The decoder writes run-length output to BytesIO without limiting expansion to the declared image size. An…

more

attacker can supply a crafted MSP image to an application that loads its pixels. This can exhaust memory and deny service even when the declared pixel count passes the decompression-bomb check. This issue is fixed in version 13.0.0.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-96637Same product: Python Pillow
CVE-2026-112398Same product: Python Pillow
CVE-2026-112406Same product: Python Pillow
CVE-2026-55379Same product: Python Pillow
CVE-2026-59205Same product: Python Pillow
CVE-2026-96639Same product: Python Pillow
CVE-2026-112897Same product: Python Pillow
CVE-2026-59197Same product: Python Pillow
CVE-2026-59200Same product: Python Pillow
CVE-2026-112402Same product: Python Pillow

Affected Assets

python
pillow
4.1.0 — 13.0.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Resource allocation controls bound memory/CPU consumption that a data-amplification attack would otherwise exhaust.

Input validation can reject or limit decompression of data whose expansion ratio exceeds safe thresholds.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure-development practices include input-validation and resource-limit checks that prevent improper handling of compressed data.

DE.CM-09 partial match
blocks

Runtime monitoring of compute resources can detect exhaustion caused by decompression bombs.

PR.IR-04 partial match
blocks

Capacity planning and monitoring directly limits the availability impact of data-amplification attacks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can uncover decompression-bomb vulnerabilities before release.

finds

Monitoring can detect anomalous resource usage but does not prevent the weakness.

prevents

Secure coding practices directly require bounds checking and safe handling of compressed data.

References