Skip to main content
VulnerabilityPublished Updated

CVE-2025-57614: Uncontrolled Resource Consumption

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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 2 Sep 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

AI-suggested

European organizations should take immediate and specific steps to mitigate this vulnerability beyond generic patching advice. First, they should identify all instances of rust-ffmpeg 0.3.0 usage within their software stacks, including indirect dependencies in third-party applications. Until an official patch is released, organizations should implement input validation and sanitization at the application level to ensure dimension parameters passed to rust-ffmpeg do not contain zero or values exceeding i32::MAX. Employing runtime application self-protection (RASP) or Web Application Firewalls (WAF) with custom rules to detect and block malformed multimedia inputs can reduce exposure. Additionally, organizations should monitor application logs for crashes or anomalous behavior indicative of exploitation attempts. Where feasible, sandboxing or containerizing applications using rust-ffmpeg can limit the impact of potential arbitrary code execution. Security teams should also engage with software vendors to prioritize patch development and apply updates promptly once available. Finally, conducting regular security assessments and fuzz testing on multimedia processing components can help uncover similar vulnerabilities proactively.

Description

An issue was discovered in rust-ffmpeg 0.3.0 (after comit 5ac0527) Integer overflow and invalid input vulnerability in the cached method allows an attacker to cause a denial of service or potentially execute arbitrary code. The vulnerability occurs when dimension parameters are zero or exceed i32::MAX, leading to an unchecked cast that violates the underlying C function's preconditions and triggers undefined behavior.

References

Community reviews

Loading reviews…