Cyber Resilience

CVE-2026-64832

Memory Safety in Ffmpeg 4.4 – 8.1.2

Public PoCMemory Safety
Published
22 July 2026
Modified
28 July 2026
Patch / advisory
View advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0033 26th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-64832 is a high-severity Double Free (CWE-415) vulnerability in Ffmpeg Ffmpeg. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to CM-7 (Least Functionality) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-415

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
attack.mitre.org →
Why these techniques?

Double-free in FFmpeg NVDEC decoder enables RCE via crafted video file (malicious file delivery + client-side exploitation).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1203 Exploitation for Client Execution Executionconfidence: HIGH
Double-free in media decoder enables arbitrary code execution via crafted video file opened by the victim.
attack.mitre.org →
T1204.002 Malicious File Executionconfidence: HIGH
Vulnerability is triggered by user opening a malicious video file in an FFmpeg-based application.
attack.mitre.org →
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2024-35365Same product: Ffmpeg Ffmpeg
CVE-2026-64830Same product: Ffmpeg Ffmpeg
CVE-2026-64831Same product: Ffmpeg Ffmpeg
CVE-2024-35368Same product: Ffmpeg Ffmpeg
CVE-2026-40962Same product: Ffmpeg Ffmpeg
CVE-2024-7055Same product: Ffmpeg Ffmpeg
CVE-2025-1594Same product: Ffmpeg Ffmpeg
CVE-2025-12343Same product: Ffmpeg Ffmpeg
CVE-2026-64835Same product: Ffmpeg Ffmpeg
CVE-2025-69693Same product: Ffmpeg Ffmpeg

Affected Assets

ffmpeg
ffmpeg
4.4 — 8.1.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • CM-7 Least Functionality
  • SI-16 Memory Protection
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-2 Flaw Remediation good match
prevent

Directly requires timely application of patches that eliminate the double-free in ff_nvdec_start_frame_sep_ref within nvdec.c.

CM-7 Least Functionality good match
prevent

Disables or restricts use of the vulnerable NVDEC hardware decoder path when the functionality is not required.

SI-16 Memory Protection partial match
prevent

Applies memory protections that can block or contain exploitation of the double-free memory corruption.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure SDLC practices directly prevent double-free errors via static analysis, safe memory APIs, and testing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect double-free conditions before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle includes memory-safety practices that can prevent double-free bugs.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate memory-safety rules that reduce double-free risk.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles can prescribe safe memory-management patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper use of free() and similar functions.

References