Skip to main content
CVE-2025-8586VulnerabilityPublished

CVE-2025-8586: libav · NULL Pointer Dereference

Affects libavSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium · end of life, no fix coming : replace or isolate libav; no fix will be released.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
None coming – the product is end of life
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 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 2026-10-25.

What to do

No fix will be released: libav is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

ProductAffectedFixed in
libavAffected
  • =12.0
  • =12.1
  • =12.2
  • =12.3
Fixed in–

AI-suggested

Given that the affected libav versions (12.0 to 12.3) are no longer supported by the maintainer and no official patches are available, European organizations should prioritize upgrading to a supported and patched version of libav or migrate to alternative actively maintained multimedia frameworks such as FFmpeg. If upgrading is not immediately feasible, organizations should implement strict access controls to limit local user access to systems running vulnerable libav versions, thereby reducing the risk of exploitation. Employing application whitelisting and monitoring for unusual process crashes related to media processing applications can help detect attempts to exploit this vulnerability. Additionally, organizations should conduct an inventory of all systems and embedded devices to identify any that use libav 12.x and plan for their timely replacement or upgrade. For critical media processing infrastructure, isolating these systems within secure network segments and applying host-based intrusion detection systems can further mitigate risk. Finally, organizations should stay informed about any future patches or security advisories related to libav and apply them promptly once available.

Description

A vulnerability, which was classified as problematic, was found in libav up to 12.3. This affects the function ff_seek_frame_binary of the file /libavformat/utils.c of the component MPEG File Parser. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The bug was initially reported by the researcher to the wrong project. This vulnerability only affects products that are no longer supported by the maintainer.

References

Community reviews

Loading reviews…