Skip to main content
CVE-2025-63757VulnerabilityPublished Updated

SUSE ffmpeg · Security update for ffmpeg-4

Affects SUSE ffmpegSource GCVE Database

0
Compare
Authoritative record:CVE-2025-63757· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 31 Oct 2026, 08:20 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. Weaponized: 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
SUSEsuse/ffmpegpkg:rpm/suse/ffmpegOther threatsAffected
  • =4.4.5-bp160.2.1.aarch64
Fixed in–

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

AI-suggested

A security update fixing CVE-2025-63757 has been released by the SUSE Product Security Team. Users of ffmpeg-4 should apply the update to remediate the integer overflow vulnerability. Patch status is not explicitly confirmed in the provided data; therefore, users should consult the official SUSE advisory for the latest remediation guidance.

Description

A security update for ffmpeg-4 addresses an integer overflow vulnerability in the yuv2ya16_X_c_template() function within the swscale/output component. This flaw is tracked as CVE-2025-63757 and has been fixed by the SUSE Product Security Team. The vulnerability is considered high severity due to the potential risks associated with integer overflows. No specific affected versions are provided in the available data.

References

Community reviews

Loading reviews…