Skip to main content
CVE-2025-8584VulnerabilityPublished

CVE-2025-8584: 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 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: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 the absence of official patches due to the affected versions being unsupported, European organizations should prioritize upgrading to a supported libav version or migrating to alternative actively maintained multimedia frameworks. If upgrading is not immediately feasible, organizations should implement strict access controls to limit local access to systems running vulnerable libav versions, minimizing the risk of exploitation. Employ application whitelisting and endpoint protection to detect and prevent unauthorized local activities. Additionally, sandboxing or containerizing applications that use libav can help contain potential crashes and prevent broader system impact. Regularly monitor system logs and application behavior for signs of crashes or abnormal activity related to media processing. Organizations should also review and update their incident response plans to address potential denial-of-service scenarios stemming from this vulnerability. Finally, consider recompiling libav with added null pointer checks or applying community-developed unofficial patches if available, while carefully testing for stability.

Description

A vulnerability classified as problematic was found in libav up to 12.3. Affected by this vulnerability is the function av_buffer_unref of the file libavutil/buffer.c of the component AVI File Parser. The manipulation leads to null pointer dereference. Local access is required to approach this attack. 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…