# CVE-2026-70632: FFmpeg 4.4 < 9.0 Heap Out-of-Bounds Write in CFHD Decoder via AVI Demuxing

> Remote attackers can achieve arbitrary code execution by supplying a crafted AVI file to FFmpeg, exploiting a heap out-of-bounds write in the CFHD decoder.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/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 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-70632, ECHO-d1bb-4d4f-3ea6, GHSA-q24x-99v6-6hxc, JLSEC-2026-1192, UBUNTU-CVE-2026-70632

## What is CVE-2026-70632?

CVE-2026-70632 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 6 Aug 2026. 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

FFmpeg versions from 4.4 up to, but not including, 9.0 contain an out-of-bounds heap write vulnerability in the native GoPro CineForm HD (CFHD) decoder that allows remote attackers to corrupt heap memory by supplying a crafted AVI file during stream probing. The cfhd_decode() function fails to enforce the non-Bayer logical output-width invariant in the transform-type-2 reconstruction path, causing horiz_filter_clip() to write oversized 16-bit sample rows far beyond the allocated output frame buffer, which can be escalated to arbitrary code execution via overwrite of a live cleanup callback pointer.

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

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Upgrade to a fixed version.

## Is CVE-2026-70632 being exploited?

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

## Other vulnerabilities in Ffmpeg Ffmpeg

- [CVE-2013-0864](https://insights.sbomify.com/CVE-2013-0864/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0872](https://insights.sbomify.com/CVE-2013-0872/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0873](https://insights.sbomify.com/CVE-2013-0873/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-4265](https://insights.sbomify.com/CVE-2013-4265/): Null dereference in n/a (critical 10.0)
- [CVE-2011-3937](https://insights.sbomify.com/CVE-2011-3937/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70632 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 6 Aug 2026. 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-2026-70632 in the wild and no public exploit code.

Affected product: Ffmpeg 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-2026-70632/ (Markdown: https://insights.sbomify.com/CVE-2026-70632/index.md)
```

## Sources

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

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