Skip to main content
CVE-2024-36618VulnerabilityPublished Updated

CVE-2024-36618: ffmpeg · n/a

Affects ffmpegSource CVE Database V5

0

Not known to be exploited · CVSS 6.2 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubffmpeg/ffmpegpkg:github/ffmpeg/ffmpegOther threatsAffected
  • =6.1.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor FFmpeg project communications and security advisories for the release of an official patch addressing CVE-2024-36618 and apply updates promptly. 2. Until patched, restrict or disable processing of untrusted AVI files in applications and services using FFmpeg 6.1.1. 3. Implement input validation and file integrity checks to detect malformed or suspicious AVI files before processing. 4. Employ sandboxing or containerization techniques to isolate media processing components, limiting the impact of potential crashes. 5. For media ingestion pipelines, enforce strict access controls and scanning of uploaded files to prevent malicious content from reaching vulnerable components. 6. Consider upgrading to a later FFmpeg version if available and confirmed to be unaffected by this vulnerability. 7. Conduct internal audits to identify all systems and applications using FFmpeg 6.1.1 to ensure comprehensive mitigation coverage. 8. Educate relevant personnel about the risks of processing untrusted media files and the importance of timely patching.

Description

FFmpeg n6.1.1 has a vulnerability in the AVI demuxer of the libavformat library which allows for an integer overflow, potentially resulting in a denial-of-service (DoS) condition.

References

Community reviews

Loading reviews…