Skip to content
Applications

CVE-2026-64831

8.7
High
EPSS 0.45%Patch availableJul 23, 2026

Stack buffer overflow in FFmpeg Vulkan HEVC decoder enabling remote code execution via crafted HEVC stream

common questions

Is CVE-2026-64831 being exploited?

Not confirmed. CVE-2026-64831 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.45% probability of exploitation in the next 30 days.

How severe is CVE-2026-64831?

CVE-2026-64831 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-64831?

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

What does CVE-2026-64831 affect?

CVE-2026-64831 affects FFmpeg 8.0 - 8.1.2, Vulkan HEVC hardware decoder (vk_hevc_end_frame), Apps using FFmpeg hardware HEVC decoding. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64831?

Disable Vulkan HEVC hardware decoding; update FFmpeg to a patched release when available.

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

executive summary
technical analysis
affected
FFmpeg 8.0 - 8.1.2Vulkan HEVC hardware decoder (vk_hevc_end_frame)Apps using FFmpeg hardware HEVC decoding
impact

Remote arbitrary code execution by supplying a crafted HEVC/H.265 bitstream to Vulkan HEVC hw decoder, overwriting return addresses.

action required

Immediate action required

affected versions
FFmpeg FFmpeg
  • affected>= 8.0 and <= 8.1.2
  • affected92737390dc133daadce47dd7d2ec8ef3d9ebcbed

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