CVE-2025-57616: rust-ffmpeg · Use After Free
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
To mitigate this vulnerability, organizations should first identify all instances where rust-ffmpeg 0.3.0 is used within their software environments. Since no official patches are currently linked, it is advisable to monitor the rust-ffmpeg repository and related security advisories for updates or patches addressing this issue. In the interim, consider the following specific actions: 1) Avoid processing untrusted or malformed multimedia data with the affected version to reduce exploitation risk. 2) Implement runtime memory safety tools such as AddressSanitizer or Rust-specific safety checks during development and testing to detect use-after-free conditions early. 3) If feasible, temporarily replace rust-ffmpeg with alternative multimedia libraries that do not have this vulnerability. 4) Employ application-level sandboxing or containerization to limit the impact of potential crashes or memory corruption. 5) Conduct thorough code reviews and static analysis focusing on unsafe Rust code and pointer usage in multimedia processing modules. 6) Prepare incident response plans for potential denial of service events related to this vulnerability. These targeted mitigations go beyond generic advice by focusing on the specific nature of the vulnerability and the affected library.
Description
An issue was discovered in rust-ffmpeg 0.3.0 (after comit 5ac0527) A use-after-free vulnerability in the write_interleaved method allows an attacker to cause a denial of service or memory corruption. The method violates Rust's aliasing rules by modifying a data structure through a mutable pointer while only holding an immutable reference, which can lead to undefined behavior when the data is accessed later.