Skip to main content
VulnerabilityPublished Updated

CVE-2024-31581: FFmpeg · Improper Validation of Array Index

Affects FFmpegSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 65% 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 17 Apr 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubffmpeg/FFmpegpkg:github/ffmpeg/FFmpegOther threatsAffected
  • =6.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

European organizations should take immediate and specific actions to mitigate CVE-2024-31581. First, they must track FFmpeg's official releases and promptly apply any security patches addressing this vulnerability. If a patch is not yet available, consider temporarily disabling or isolating FFmpeg-dependent services that process untrusted media inputs. Implement strict input validation and sanitization on all media files before processing to reduce the risk of malformed data triggering the vulnerability. Employ sandboxing or containerization techniques to limit the impact of potential exploitation by isolating FFmpeg processes from critical system components. Network segmentation can help restrict access to media processing services. Monitor logs and network traffic for anomalies indicative of exploitation attempts, such as crashes or unusual memory access patterns. Additionally, update intrusion detection and prevention systems with signatures related to this vulnerability once available. Engage with vendors and service providers to confirm their remediation status and ensure third-party software incorporating FFmpeg is also updated. Finally, conduct security awareness training for developers and system administrators about the risks of processing untrusted media content.

Description

FFmpeg version n6.1 was discovered to contain an improper validation of array index vulnerability in libavcodec/cbs_h266_syntax_template.c. This vulnerability allows attackers to cause undefined behavior within the application.

References

Community reviews

Loading reviews…