Skip to main content
VulnerabilityPublished Updated

CVE-2025-57613: rust-ffmpeg · NULL Pointer Dereference

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 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 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: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

To mitigate CVE-2025-57613, organizations should first identify all instances where rust-ffmpeg 0.3.0 is used, particularly focusing on components that utilize the input() constructor function. Until an official patch is released, developers should implement defensive programming practices such as explicitly checking the return value of avio_alloc_context() for NULL before storing or dereferencing it. Adding robust error handling to gracefully manage allocation failures will prevent the null pointer dereference and subsequent crashes. Application-level mitigations include deploying runtime monitoring and crash detection to quickly identify and respond to DoS conditions. Network-level protections such as rate limiting and input validation can reduce the likelihood of triggering the vulnerability via malformed inputs. Organizations should also track updates from rust-ffmpeg maintainers and apply patches promptly once available. For critical systems, consider isolating or sandboxing media processing components to limit the impact of potential crashes. Finally, conducting thorough code reviews and fuzz testing around the affected functions can help uncover similar issues proactively.

Description

An issue was discovered in rust-ffmpeg 0.3.0 (after comit 5ac0527) A null pointer dereference vulnerability in the input() constructor function allows an attacker to cause a denial of service. The vulnerability is triggered when the avio_alloc_context() call fails and returns NULL, which is then stored and later dereferenced by the Io struct's Drop implementation.

References

Community reviews

Loading reviews…