Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2026-30999 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Ffmpeg Ffmpeg. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 37th 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 SI-10 (Information Input Validation) and SI-16 (Memory Protection) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-30999 is a heap buffer overflow vulnerability, classified under CWE-122, affecting the av_bprint_finalize() function in FFmpeg version 8.0.1. Published on 2026-04-13, it enables attackers to trigger a Denial of Service (DoS) condition via a specially crafted input. The issue carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating high severity primarily due to its impact on availability.
The vulnerability can be exploited by remote, unauthenticated attackers requiring no privileges or user interaction, with low attack complexity over the network. Exploitation involves processing a malicious input, leading to a heap buffer overflow that crashes the affected FFmpeg instance and disrupts service availability, without compromising confidentiality or integrity.
Key references include a Notion site documenting CVE-2026-30999, FFmpeg doxygen source for zmqsend.c (version 7.0), the GitHub repository source for tools/zmqsend.c, and the official FFmpeg download page. Security practitioners should review these resources for code analysis and updates to address the vulnerability in FFmpeg deployments.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-21976
Vulnerability Data
A heap buffer overflow in the av_bprint_finalize() function of FFmpeg v8.0.1 allows attackers to cause a Denial of Service (DoS) via a crafted input.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Heap buffer overflow in FFmpeg enables remote unauthenticated attackers to crash the application via crafted input, directly mapping to application exploitation for endpoint DoS.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly remediates the heap buffer overflow flaw in FFmpeg's av_bprint_finalize() function through timely patching or updates to prevent DoS exploitation.
Validates and sanitizes crafted inputs before processing by FFmpeg to block heap buffer overflows triggered by malicious media files.
Implements memory protections like ASLR and heap canaries to mitigate the effects of heap buffer overflows in FFmpeg, preventing reliable DoS crashes.
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.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.
Timely patching removes known heap-overflow instances after they exist.
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.
Security testing in development and acceptance can detect heap overflows before release.
Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.
Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.
Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.
Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.
Change management ensures controlled deployment of fixes for discovered heap-overflow vulnerabilities.