CVE-2026-39217: Heap Buffer Overflow in FFmpeg VP9 Decoder
CVE-2026-39217 is a heap buffer overflow vulnerability in FFmpeg's VP9 decoder. The issue is described as a regression introduced in March 2025. Successful exploitation occurs when the decoder processes attacker-controlled VP9 media data and performs an out-of-bounds write on heap-allocated memory. As a memory corruption flaw in a media parsing and decoding path, the vulnerability can be triggered during handling of crafted VP9 content by applications or services that rely on FFmpeg for decoding.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can cause memory corruption in the FFmpeg process. Depending on the surrounding application context, this may result in process crash and denial of service, and may also create conditions for arbitrary code execution if the heap corruption can be controlled reliably. Any product or workflow that decodes untrusted VP9 media through FFmpeg may be affected.
Mitigation
If you can’t patch tonight, do this now.
Until patched builds can be deployed, reduce exposure by preventing FFmpeg from decoding untrusted or externally supplied VP9 media, especially in automated or network-reachable processing pipelines. Where operationally feasible, disable or isolate VP9 decoding paths, sandbox FFmpeg-based workloads, and restrict ingestion sources to trusted content only. Additional hardening such as process isolation and memory-safety defenses may reduce exploit reliability but does not eliminate the underlying flaw.
Remediation
Patch, then assume compromise.
Apply the upstream FFmpeg fix for CVE-2026-39217 or update to a vendor or distribution package that includes the patch. Because the issue is identified as a regression from March 2025, remediation should focus on upgrading to a build that contains the post-fix VP9 decoder changes rather than retaining affected intermediate versions.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-39217 exploited in the wild?
- As of Jul 20, 2026, Mallory has no reports of CVE-2026-39217 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-39217?
- As of Jul 20, 2026, Mallory has found no public exploit for CVE-2026-39217.
- Is there a patch for CVE-2026-39217?
- Apply the upstream FFmpeg fix for CVE-2026-39217 or update to a vendor or distribution package that includes the patch. Because the issue is identified as a regression from March 2025, remediation should focus on upgrading to a build that contains the post-fix VP9 decoder changes rather than retaining affected intermediate versions.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.