# CVE-2025-59732: Heap-buffer-overflow write in FFmpeg EXR dwa_uncompress

> Heap buffer overflow in FFmpeg's EXR decoder allows attackers to corrupt memory and potentially execute code via crafted images.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-59732, GHSA-qr3p-83wm-px3f, JLSEC-2026-645, MINI-h999-qfw2-jwv8

## What is CVE-2025-59732?

CVE-2025-59732 is a high-severity memory corruption vulnerability in FFmpeg, published on 6 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

When decoding an OpenEXR file that uses DWAA or DWAB compression, there's an implicit assumption that the height and width are divisible by 8.

If the height or width of the image is not divisible by 8, the copy loops at [0] and [1] will continue to write until the next multiple of 8.

The buffer td->uncompressed_data is allocated in decode_block based on the precise height and width of the image, so the "rounded-up" multiple of 8 in the copy loop can exceed the buffer bounds, and the write block starting at [2] can corrupt following heap memory.

We recommend upgrading to version 8.0 or beyond.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2025-59732 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59732 and fix it if it is affected.

What it is: CVE-2025-59732 is a high-severity memory corruption vulnerability in FFmpeg, published on 6 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-59732 in the wild and no public exploit code.

Affected product: FFmpeg. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-59732/ (Markdown: https://insights.sbomify.com/CVE-2025-59732/index.md)
```

## Sources

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

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