CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NHigh (8.7) in python pillow. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in pillow 12.3.0.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hpillow (PyPI): fixed in 12.3.0Explain CVE-2026-59204 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59204?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59204?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59204 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| python:pillow | from 8.2.0 before 12.3.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-vjc4-5qp5-m44j | PyPI | pillow | >=8.2.0 <12.3.0 | 12.3.0 |
| PYSEC-2026-3496 | PyPI | pillow | >=8.2.0 <12.3.0 | 12.3.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | pillow | no fix listed | DEBIAN-CVE-2026-59204 |
| Debian | 14 | pillow | 12.3.0-1 | DEBIAN-CVE-2026-59204 |
| Ubuntu | 22.04:LTS | pillow | 9.0.1-1ubuntu0.6 | UBUNTU-CVE-2026-59204 USN-8999-1 |
| Ubuntu | 24.04:LTS | pillow | 10.2.0-1ubuntu1.4 | UBUNTU-CVE-2026-59204 USN-8999-1 |
| Ubuntu | 26.04:LTS | pillow | 12.1.1-2ubuntu1.4 | UBUNTU-CVE-2026-59204 USN-8999-1 |
| Ubuntu | Pro:14.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS | pillow | no fix listed | UBUNTU-CVE-2026-59204 |
| Ubuntu | Pro:20.04:LTS | pillow, pillow-python2 | no fix listed | UBUNTU-CVE-2026-59204 |
| SUSE | Linux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 more | python-Pillow | 9.5.0-150400.5.25.1 | SUSE-SU-2026:3268-1 |
| SUSE | Linux Enterprise Module for Package Hub 15 SP7 | python-Pillow | 7.2.0-150300.3.30.1 | SUSE-SU-2026:3084-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | python-Pillow | 11.3.0-160000.8.1 | SUSE-SU-2026:23217-1 SUSE-SU-2026:23228-1 |
| openSUSE | Leap 16.0 | python-Pillow | 11.3.0-160000.8.1 | openSUSE-SU-2026:21544-1 |
| openSUSE | Tumbleweed | python-Pillow | 12.3.0-2.1 | openSUSE-SU-2026:11283-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.
Red Hat rates this Important.
The impact is limited to denial of service via excessive memory allocation. A crafted JPEG2000 file can trigger out-of-memory failures, but this does not lead to code execution or information disclosure.
If the application does not need JPEG2000 support, block .jp2, .j2k, .jpf, and .jpx uploads at the input layer.
For services that do process JPEG2000, set memory limits on the process or container (LimitAS= in systemd, or memory limits in Kubernetes/Podman) so a crafted image can only crash the worker, not the whole host. Add automatic restarts (Restart=always in systemd, or container restart policies) so the service recovers from OOM kills without someone having to intervene.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat AI Inference Server 3.2 | rhaiis/vllm-cuda-rhel9:1787860580 | Fixed 2026-08-31 | RHSA-2026:61627 |
| Red Hat AI Inference Server 3.2 | rhaiis/model-opt-cuda-rhel9:1787772157 | Fixed 2026-08-31 | RHSA-2026:61628 |
| Red Hat AI Inference Server 3.2 | rhaiis/vllm-rocm-rhel9:1787884873 | Fixed 2026-08-31 | RHSA-2026:61629 |
| Red Hat AI Inference Server 3.3 | rhaiis/model-opt-cuda-rhel9:1787601159 | Fixed 2026-08-25 | RHSA-2026:59518 |
| Red Hat AI Inference Server 3.4 | rhaii/vllm-spyre-rhel9:1789681201 | Fixed 2026-09-21 | RHSA-2026:69464 |
| Red Hat AI Inference Server 3.4 | rhaii/vllm-cpu-rhel9:1789681128 | Fixed 2026-09-21 | RHSA-2026:69466 |
| Red Hat AI Inference Server 3.4 | rhaii/vllm-cuda-rhel9:1789681126 | Fixed 2026-09-21 | RHSA-2026:69467 |
| Red Hat AI Inference Server 3.4 | rhaii/model-opt-cuda-rhel9:1789681126 | Fixed 2026-09-21 | RHSA-2026:69468 |
| Red Hat AI Inference Server 3.4 | rhaii/vllm-rocm-rhel9:1789681126 | Fixed 2026-09-21 | RHSA-2026:69469 |
| Red Hat AI Inference Server 3.4 | rhaii/vllm-cpu-rhel9:1790075793 | Fixed 2026-09-23 | RHSA-2026:70965 |
| Exploit Intelligence | exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 | Fix deferred | |
| Lightspeed Core | lightspeed-core/lightspeed-stack-rhel9 | Affected | |
| Lightspeed Core | lightspeed-core/rag-tool-cpu-rhel9 | Affected | |
| Lightspeed Core | lightspeed-core/rag-tool-cuda-12.9-rhel9 | Affected | |
| OpenShift Lightspeed | openshift-lightspeed/lightspeed-ocp-rag-rhel9 | Not affected | |
| OpenShift Lightspeed | openshift-lightspeed/lightspeed-service-api-rhel9 | Affected | |
| OpenShift Lightspeed | openshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9 | Not affected | |
| Red Hat AI Inference Server | rhaiis/vllm-cpu-rhel9 | Will not fix | |
| Red Hat AI Inference Server | rhaiis/vllm-neuron-rhel9 | Will not fix | |
| Red Hat AI Inference Server | rhaiis/vllm-spyre-rhel9 | Affected | |
| 79 more in the JSON and on Red Hat's page. | |||
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-59204.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).