CVE-2026-64834
FFmpeg RTP/ASF demuxer infinite loop allows CPU exhaustion and denial of service.
Is CVE-2026-64834 being exploited?
Not confirmed. CVE-2026-64834 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.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-64834?
CVE-2026-64834 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-64834?
Yes. A fix has been recorded for CVE-2026-64834. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64834 affect?
CVE-2026-64834 affects FFmpeg 0.6.3 - 8.1.2, libavformat RTP/ASF demuxer (rtpdec_asf.c). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64834?
Upgrade FFmpeg to a patched release and block/untrusted RTP/ASF streams at ingress.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can send crafted RTP/ASF streams to trigger an infinite loop in the RTP/ASF demuxer, causing CPU exhaustion and denial of service.
Patch when possible
- affected>= 0.6.3 and <= 8.1.2
- affected11d5f475be95d22d5f0692220cc772b116abc632
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.