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

> A heap-buffer-overflow in FFmpeg's EXR decoder allows attackers to execute arbitrary code or cause denial of service via crafted files.

- **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-59733, GHSA-hpfq-c235-5854, JLSEC-2026-646, MINI-xgfq-qpw9-rcvf

## What is CVE-2025-59733?

CVE-2025-59733 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 all image channels have the same pixel type (and size), and that if there are four channels, the first four are "B", "G", "R" and "A". The channel parsing code can be found in decode_header. The buffer td->uncompressed_data is allocated in decode_block based on the xsize, ysize and computed current_channel_offset.

The function dwa_uncompress then assumes at [5] that if there are 4 channels, these are "B", "G", "R" and "A", and in the calculations at [6] and [7] that all channels are of the same type, which matches the type of the main color channels.

If we set the main color channels to a 4-byte type and add duplicate or unknown channels of the 2-byte EXR_HALF type, then the addition at [7] will increment the pointer by 4-bytes * xsize * nb_channels, which will exceed the allocated buffer.

We recommend upgrading to version 8.0 or beyond.

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

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


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

Upgrade to a fixed version.

## Is CVE-2025-59733 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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