# CVE-2025-59734: Heap-buffer-overflow write in FFmpeg SANM process_ftch

> A use-after-free vulnerability in FFmpeg's SANM 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:** GHSA-g9mr-r3g9-6594, JLSEC-2026-647, MINI-qvwf-6r7r-3h22, UBUNTU-CVE-2025-59734

## What is CVE-2025-59734?

CVE-2025-59734 is a high-severity use after free 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

It is possible to cause an use-after-free write in SANM decoding with a carefully crafted animation using subversion <2.

When a STOR chunk is present, a subsequent FOBJ chunk will be saved in ctx->stored_frame. Stored frames can later be referenced by FTCH chunks. For files using subversion < 2, the undecoded frame is stored, and decoded again when the FTCH chunks are parsed. However, in process_frame_obj if the frame has an invalid size, there’s an early return, with a value of 0. 

This causes the code in decode_frame to still store the raw frame buffer into ctx->stored_frame. Leaving ctx->has_dimensions set to false.

A subsequent chunk with type FTCH would call process_ftch and decode that frame obj again, adding to the top/left values and calling process_frame_obj again.
Given that we never set ctx->have_dimensions before, this time we set the dimensions, calling init_buffers, which can reallocate the buffer in ctx->stored_frame, freeing the previous one. However, the GetByteContext object gb still holds a reference to the old buffer.

Finally, when the code tries to decode the frame, codecs that accept a GetByteContext as a parameter will trigger a use-after-free read when using gb.

GetByteContext is only used for reading bytes, so at most one could read invalid data. There are no heap allocations between the free and when the object is accessed. However, upon returning to process_ftch, the code restores the original values for top/left in stored_frame, writing 4 bytes to the freed data at offset 6, potentially corrupting the allocator’s metadata.

This issue can be triggered just by probing whether a file has the sanm format.

We recommend upgrading to version 8.0 or beyond.

Weakness: CWE-416 (Use After Free)

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


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

Upgrade to a fixed version.

## Is CVE-2025-59734 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59734 is a high-severity use after free 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-59734 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-59734/ (Markdown: https://insights.sbomify.com/CVE-2025-59734/index.md)
```

## Sources

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

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