CVE-2026-64832 is a double-free vulnerability in FFmpeg versions 4.4 through 8.1.2 in the NVIDIA NVDEC hardware-decoding implementation. When decoder surfaces are exhausted, an error path in ff_nvdec_start_frame_sep_ref releases frame-description private data through nvdec_fdd_priv_free, after which the calling layer releases the same data again. This results in a double-free of the underlying decoder context when crafted video content is processed by an FFmpeg-based application using NVDEC acceleration.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity security vulnerability fixed through the FFmpeg 9.0.1 Fedora 45 update; no technical flaw details are provided.
A vulnerability in the Ubuntu-packaged FFmpeg ecosystem; flaw details are not provided.
A specific FFmpeg vulnerability included in AISLE's public registry growth summary.
A double-free vulnerability in FFmpeg's NVIDIA NVDEC hardware decoder (libavcodec/nvdec.c) that can cause memory corruption when a crafted video file is processed by FFmpeg-based applications using NVDEC hardware-accelerated decoding.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.