# CVE-2025-48379: Pillow Vulnerable to Write Buffer Overflow on BCn encoding

> A heap buffer overflow in Pillow allows attackers to execute arbitrary code or cause denial of service when saving large untrusted DDS images.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jul 2025
- **Updated:** 1 Jul 2025
- **Also known as:** BIT-pillow-2025-48379, CLSA-2026-1772410259, GHSA-xg8h-j46f-w952, PYSEC-2025-61, ROOT-APP-PYPI-CVE-2025-48379, openSUSE-SU-2025:15316-1

## What is CVE-2025-48379?

CVE-2025-48379 is a high-severity memory corruption vulnerability in Python Pillow, published on 1 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Pillow is a Python imaging library. In versions 11.2.0 to before 11.3.0, there is a heap buffer overflow when writing a sufficiently large (>64k encoded with default settings) image in the DDS format due to writing into a buffer without checking for available space. This only affects users who save untrusted data as a compressed DDS image. This issue has been patched in version 11.3.0.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-48379?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pillow` | Bitnami | From 11.2.0 | None |
| `pillow` | PyPI | From 11.2.0 | 11.3.0 |
| `pillow` | PyPI | From 11.2.0 | 11.3.0 |
| `pillow` | PyPI | From 11.2.0 | 11.3.0 |
| `python-Pillow` | openSUSE:Tumbleweed | All versions | 11.3.0-1.1 |

Products: Python Pillow.

## How do I fix CVE-2025-48379?

Upgrade pillow to 11.3.0 or later.

## Is CVE-2025-48379 being exploited?

There is no known exploitation of CVE-2025-48379 in the wild and no public exploit code.

## 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-2025-48379 and fix it if it is affected.

What it is: CVE-2025-48379 is a high-severity memory corruption vulnerability in Python Pillow, published on 1 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48379 in the wild and no public exploit code.

Affected packages and fixed versions:
- pillow (Bitnami): affected from 11.2.0; no fix listed
- pillow (PyPI): affected from 11.2.0; fixed in 11.3.0
- pillow (PyPI): affected from 11.2.0; fixed in 11.3.0
- pillow (PyPI): affected from 11.2.0; fixed in 11.3.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-2025-48379/ (Markdown: https://insights.sbomify.com/CVE-2025-48379/index.md)
```

## Sources

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

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