# CVE-2026-112392: Pillow: NULL dereference in ImagingExpand via rank filters on zero-size images

> An attacker can cause a native process crash in Pillow by supplying a zero-size image to rank-based filters, leading to a null pointer dereference.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** BIT-pillow-2026-112392, DEBIAN-CVE-2026-112392, ECHO-8e8c-c813-2f3f, GHSA-27h8-gf7j-v5hc, PYSEC-2026-4326, ROOT-APP-PYPI-CVE-2026-112392, UBUNTU-CVE-2026-112392

## What is CVE-2026-112392?

CVE-2026-112392 is a high-severity vulnerability in Python Pillow, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pillow is a Python imaging library. Prior to 13.0.0, Pillow's rank-based filters can dereference invalid image storage for a zero-size image. ImagingExpand() allocates a non-empty output and then faults while replicating edges by reading the first pixel from empty input storage; ImagingRankFilter is never reached. An attacker can supply or cause creation of a zero-size image to an application that applies a rank, median, minimum, or maximum filter. This causes a native process crash. This issue is fixed in version 13.0.0.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-112392?

4 open source packages ship an affected version, including pillow and Pillow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pillow` | Bitnami | All versions | 13.0.0 |
| `pillow` | PyPI | All versions | 13.0.0 |
| `pillow` | PyPI | All versions | 13.0.0 |
| `Pillow` | PyPI | All versions | 13.0.0 |

Products: Python Pillow.

## How do I fix CVE-2026-112392?

Upgrade pillow to 13.0.0 or later.

## Is CVE-2026-112392 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112392 exists.

## Other vulnerabilities in Python Pillow

- [CVE-2014-3007](https://insights.sbomify.com/CVE-2014-3007/): Pillow command injection (critical 10.0)
- [CVE-2026-96639](https://insights.sbomify.com/CVE-2026-96639/): Pillow multi-frame loaders can reuse stale native image storage after mode transitions (critical 9.8)
- [CVE-2022-30595](https://insights.sbomify.com/CVE-2022-30595/): Buffer over-flow in Pillow (critical 9.8)
- [CVE-2021-25289](https://insights.sbomify.com/CVE-2021-25289/): Out of bounds write in Pillow (critical 9.8)
- [CVE-2016-4009](https://insights.sbomify.com/CVE-2016-4009/): Pillow Integer overflow in ImagingResampleHorizontal (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112392 and fix it if it is affected.

What it is: CVE-2026-112392 is a high-severity vulnerability in Python Pillow, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112392 exists.

Affected packages and fixed versions:
- pillow (Bitnami): affected all versions; fixed in 13.0.0
- pillow (PyPI): affected all versions; fixed in 13.0.0
- pillow (PyPI): affected all versions; fixed in 13.0.0
- Pillow (PyPI): affected all versions; fixed in 13.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112392/ (Markdown: https://insights.sbomify.com/CVE-2026-112392/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112392
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112392
- OSV: https://osv.dev/vulnerability/CVE-2026-112392

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112392/
Summaries are generated and may contain mistakes; the official description above is the record.