Skip to content
Applications

CVE-2026-64832

8.7
High
EPSS 0.34%Patch availableJul 23, 2026

Double-free in FFmpeg NVDEC allows crafted videos to crash or enable RCE.

common questions

Is CVE-2026-64832 being exploited?

Not confirmed. CVE-2026-64832 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-64832?

CVE-2026-64832 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-64832?

Yes. A fix has been recorded for CVE-2026-64832. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64832 affect?

CVE-2026-64832 affects FFmpeg 4.4 - 8.1.2, Applications using FFmpeg with NVIDIA NVDEC, Media players, Streaming servers, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64832?

Upgrade to a patched FFmpeg or disable NVDEC hardware decoding; block untrusted video inputs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
FFmpeg 4.4 - 8.1.2Applications using FFmpeg with NVIDIA NVDECMedia playersStreaming serversVideo processing pipelines
impact

Crafted video triggers double-free in NVDEC causing memory corruption; can crash processes or enable remote code execution in FFmpeg-based apps using NVIDIA hardware decoding.

action required

Patch when possible

affected versions
FFmpeg FFmpeg
  • affected>= 4.4 and <= 8.1.2
  • affected4c6217477fc64305055b37d9d1d0d76d30e37f97

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free