CVE-2024-35367: FFmpeg · Out-of-bounds Read
Affects FFmpegSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubffmpeg/FFmpegpkg:github/ffmpeg/FFmpegOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Monitor FFmpeg vendor channels and security advisories for official patches addressing CVE-2024-35367 and apply updates promptly once available.
- Until patches are released, restrict or sandbox the processing of untrusted or unauthenticated media inputs to minimize exposure.
- Employ network-level filtering and intrusion detection systems to monitor for anomalous traffic patterns targeting media processing services.
- Use application-layer firewalls or media gateways to validate and sanitize incoming media streams before processing with FFmpeg.
- Where feasible, disable or avoid using the PowerPC-specific VP8 DSP code paths if not required, or compile FFmpeg without the vulnerable module.
- Conduct internal audits to identify all systems and applications utilizing FFmpeg 6.1.1 or related versions and prioritize remediation efforts accordingly.
- Implement robust logging and monitoring to detect crashes or unusual behavior indicative of exploitation attempts.
- Educate development and operations teams about the vulnerability to ensure rapid response and patch deployment.
- For cloud or third-party media services, verify vendor patching status and consider alternative providers if timely mitigation is not assured.
Description
FFmpeg n6.1.1 has an Out-of-bounds Read via libavcodec/ppc/vp8dsp_altivec.c, static const vec_s8 h_subpel_filters_outer
References
- github.com/ffmpeg/ffmpeg/commit/09e6840cf7a3ee07a73c3ae88a020bf27ca1a667 (opens in a new tab)
- github.com/FFmpeg/FFmpeg/blob/n6.1.1/libavcodec/ppc/vp8dsp_altivec.c (opens in a new tab)
- gist.github.com/1047524396/9754a44845578358f6a403447c458ca4 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/02/msg00000.html (opens in a new tab)