Skip to main content
VulnerabilityPublished

CVE-2025-63757: FFmpeg · Integer Overflow

Affects FFmpegSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% 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:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Dec 2025

  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
  • =8.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

  1. Monitor official FFmpeg channels and security advisories for patches addressing CVE-2025-63757 and apply updates promptly once available.
  2. Until patches are released, implement strict input validation and filtering to block malformed or suspicious multimedia files from untrusted sources.
  3. Employ sandboxing or containerization to isolate FFmpeg processes, limiting the impact of potential crashes on broader systems.
  4. Restrict network exposure of services that process multimedia content using FFmpeg to trusted users or internal networks only.
  5. Use application-layer firewalls or intrusion prevention systems to detect and block anomalous multimedia payloads.
  6. Conduct regular security assessments and fuzz testing on multimedia processing components to identify similar vulnerabilities proactively.
  7. Maintain comprehensive logging and monitoring to detect unusual crashes or service disruptions linked to FFmpeg usage.
  8. Educate developers and system administrators about the risks of integer overflow vulnerabilities and secure coding practices related to multimedia processing.

Description

Integer overflow vulnerability in the yuv2ya16_X_c_template function in libswscale/output.c in FFmpeg 8.0.

References

Community reviews

Loading reviews…