# CVE-2026-64832: FFmpeg 4.4 - 8.1.2 Double-Free in NVDEC Hardware Decoder via nvdec.c

> Attackers can trigger memory corruption and potential code execution in FFmpeg applications using NVDEC hardware decoding by supplying a crafted video file.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-64832, ECHO-7190-6b4d-bcce, GHSA-jc8j-9799-c943, JLSEC-2026-1174, MINI-x2cf-pm64-2f5r, UBUNTU-CVE-2026-64832

## What is CVE-2026-64832?

CVE-2026-64832 is a high-severity use after free vulnerability in Ffmpeg Ffmpeg, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

FFmpeg versions 4.4 through 8.1.2 contain a double-free vulnerability in the NVIDIA NVDEC hardware decoder within libavcodec/nvdec.c that allows attackers to trigger memory corruption by supplying a crafted video file. When no decoder surfaces remain, the ff_nvdec_start_frame_sep_ref error path frees memory via nvdec_fdd_priv_free while the calling layer subsequently frees the same frame description data, resulting in a double-free of the underlying decoder context in any FFmpeg-based application using NVDEC hardware-accelerated decoding.

Weakness: CWE-415 (Double Free)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Apply the vendor's patch.

## Is CVE-2026-64832 being exploited?

There is no known exploitation of CVE-2026-64832 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-64832 and fix it if it is affected.

What it is: CVE-2026-64832 is a high-severity use after free vulnerability in Ffmpeg Ffmpeg, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-64832 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-64832/ (Markdown: https://insights.sbomify.com/CVE-2026-64832/index.md)
```

## Sources

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

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