Skip to main content
CVE-2024-35368VulnerabilityPublished Updated

CVE-2024-35368: ffmpeg · n/a

Affects ffmpegSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% 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:H/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-26.

What to do

Affected software

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

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

AI-suggested

Until official patches are released, organizations should implement the following mitigations: 1) Restrict and validate all untrusted media inputs processed by FFmpeg to minimize exposure to crafted malicious files. 2) Employ application-level sandboxing or containerization to isolate FFmpeg processes and limit the impact of potential exploitation. 3) Monitor system and application logs for crashes or abnormal behavior related to media processing components. 4) Update intrusion detection and prevention systems with signatures targeting anomalous FFmpeg activity once available. 5) Engage with vendors and upstream FFmpeg maintainers to track patch releases and apply updates promptly. 6) For embedded systems, consider firmware updates or disabling vulnerable features if feasible. 7) Conduct internal audits to identify all FFmpeg usage within the organization to ensure comprehensive coverage of mitigation efforts. These steps go beyond generic advice by focusing on containment, input validation, and proactive monitoring tailored to this specific vulnerability.

Description

FFmpeg n7.0 is affected by a Double Free via the rkmpp_retrieve_frame function within libavcodec/rkmppdec.c.

References

Community reviews

Loading reviews…