Skip to main content
VulnerabilityPublished

CVE-2025-8585: libav · Double Free

Affects libavSource CVE Database V5

0

Public exploit available · CVSS 4.8 Medium · end of life, no fix coming : replace or isolate libav; no fix will be released.

Data as of 26 Oct 2026, 12:55 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 12% 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:L/VI:L/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: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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.3
4 affected builds
Fixed in–

AI-suggested

Given the absence of official patches, European organizations should prioritize the following mitigations: 1) Identify and inventory all systems using libav versions 12.0 to 12.3, focusing on media processing servers and embedded devices. 2) Upgrade to supported, patched versions of libav or alternative actively maintained multimedia frameworks to eliminate the vulnerability. 3) If upgrading is not immediately feasible, implement strict access controls to limit local user access to trusted personnel only, reducing the risk of exploitation. 4) Employ application sandboxing or containerization to isolate libav processes and minimize potential damage from exploitation. 5) Monitor system logs for unusual crashes or memory errors indicative of exploitation attempts. 6) Develop internal patches or backported fixes if possible, leveraging community or security researcher resources. 7) Conduct security awareness training to prevent unauthorized local access and reinforce endpoint security. These targeted steps go beyond generic advice by focusing on legacy system identification, access restriction, and containment strategies specific to this vulnerability.

Description

A vulnerability, which was classified as critical, has been found in libav up to 12.3. Affected by this issue is the function main of the file /avtools/avconv.c of the component DSS File Demuxer. The manipulation leads to double free. Attacking locally is a requirement. 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…