Cyber Resilience

CVE-2026-64834

DoS in Ffmpeg 0.6.3 – 8.1.2

Public PoCDoS
Published
22 July 2026
Modified
28 July 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0050 42th percentile
Risk Priority 46 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-64834 is a high-severity Infinite Loop (CWE-835) vulnerability in Ffmpeg Ffmpeg. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

FFmpeg versions 0.6.3 through 8.1.2 contain an infinite loop vulnerability in the RTP/ASF demuxer within libavformat/rtpdec_asf.c that allows remote attackers to cause denial of service by sending a crafted RTP/ASF stream. The rtp_asf_fix_header function fails to validate a minimum chunksize…

more

when iterating over ASF objects, causing the loop pointer to never advance when a chunksize is smaller than the 24-byte minimum ASF object header size, resulting in CPU exhaustion that denies service to legitimate users.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-25469Same product: Ffmpeg Ffmpeg
CVE-2025-10256Same product: Ffmpeg Ffmpeg
CVE-2023-6603Same product: Ffmpeg Ffmpeg
CVE-2024-55069Same product: Ffmpeg Ffmpeg
CVE-2025-1373Same product: Ffmpeg Ffmpeg
CVE-2026-30998Same product: Ffmpeg Ffmpeg
CVE-2026-66037Same product: Ffmpeg Ffmpeg
CVE-2024-35365Same product: Ffmpeg Ffmpeg
CVE-2024-35368Same product: Ffmpeg Ffmpeg
CVE-2026-64832Same product: Ffmpeg Ffmpeg

Affected Assets

ffmpeg
ffmpeg
0.6.3 — 8.1.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover unreachable loop exit conditions through static analysis, fuzzing, or execution tracing.

Flaw remediation processes identify and correct infinite-loop defects reported from testing or operations.

Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-01 partial match
prevents

Static analysis and vuln scanning during asset assessment can detect unreachable loop exits.

PR.PS-06 partial match
prevents

Secure SDLC practices (reviews, testing, static analysis) directly prevent introduction of infinite-loop defects.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.

prevents

Application security requirements can specify loop-termination rules, indirectly reducing the weakness.

prevents

Secure coding standards directly address loop termination and prevent infinite loops.

finds

Security testing can uncover infinite-loop conditions before release.

References