CVE-2024-35369: FFmpeg · Integer Overflow or Wraparound
Affects FFmpegSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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 official channels for patches addressing CVE-2024-35369 and apply updates promptly once available.
- Until patches are released, implement strict input validation and sanitization on media files, especially those containing Speex audio streams, to detect and block malformed extradata.
- Employ sandboxing or containerization for media processing applications to isolate potential crashes and limit impact on the host system.
- Restrict local access to systems processing untrusted media files to trusted users only, reducing the risk of malicious file execution.
- Use application-level monitoring to detect abnormal crashes or behavior in media decoding processes and trigger alerts for investigation.
- Educate users about the risks of opening untrusted media files and encourage cautious handling to prevent inadvertent triggering of the vulnerability.
- Consider disabling Speex codec support in FFmpeg builds if not required by the application to reduce the attack surface.
Description
In FFmpeg version n6.1.1, specifically within the avcodec/speexdec.c module, a potential security vulnerability exists due to insufficient validation of certain parameters when parsing Speex codec extradata. This vulnerability could lead to integer overflow conditions, potentially resulting in undefined behavior or crashes during the decoding process.