Skip to main content
VulnerabilityPublished

CVE-2026-125223: FFmpeg · Memory Leak

Affects FFmpegSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.7 Medium.

Data as of 9 Nov 2026, 20:20 UTC

CVSS 4.0 base score
5.7Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.7
CNA (VulnCheck)CVSS 3.14.7
CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
FFmpegFFmpegAffected
  • >=8.0 <=9.0.2
Fixed in–
GitHubFFmpegpkg:github/FFmpegOther threatsAffected
  • >=8.0 <=9.0.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, avoid processing untrusted VP9 streams with slice threading enabled or implement resource limits to mitigate memory exhaustion risk.

Description

A memory leak vulnerability exists in FFmpeg versions 8.0 through 9.0.2 in the VP9 decoder. The issue arises because the function vp9_decode_frame() does not reset the CBS fragment on error paths, leading to leaked packet buffers and units when decoding crafted VP9 streams with invalid tile sizes using slice threading. This can cause memory exhaustion in the decoding application.

References

Community reviews

Loading reviews…