FFmpeg through 9.0.2 Heap Buffer Overflow via liboapv APV Encoder Wrapper
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. FFmpeg versions 8.0 through 9.0.2 are affected Input frames are larger than the configured encoder dimensions Video is transcoded to APV without rescaling, with resolution changing mid-stream
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
FFmpeg through 9.0.2 contains a heap buffer overflow vulnerability in liboapve_encode() in libavcodec/liboapvenc.c that allows attackers to corrupt heap memory by supplying frames larger than the configured encoder dimensions. Attackers can craft videos whose resolution changes mid-stream so that transcoding to APV without rescaling writes attacker-controlled pixel data past the imgb plane buffers.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.3/10CVSS 7.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
FFmpeg versions 8.0 through 9.0.2 are affected Input frames are larger than the configured encoder dimensions Video is transcoded to APV without rescaling, with resolution changing mid-streamApply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- FFmpeg FFmpeg
From 8.0 · through 9.0.2
Evidence 5
- Patch
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125196
Is CVE-2026-125196 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The APV encoder wrapper in FFmpeg can write pixel data past the end of its image plane buffers when given frames larger than the encoder was configured for. This corrupts heap memory with attacker-controlled pixel data.Source: vulncheck.com
Which versions are affected by CVE-2026-125196?
FFmpeg: from 8.0 through 9.0.2.Source: cve.now feed data
Am I affected, and how do I check?
FFmpeg versions 8.0 through 9.0.2 are affected, but only when video is transcoded to APV without rescaling and the resolution changes mid-stream so frames exceed the configured encoder dimensions. To check a version, run ffmpeg -version and compare the number with that range.Source: vulncheck.com
How do I fix CVE-2026-125196?
The facts do not name a fixed release, so no specific upgrade target is confirmed. Check the FFmpeg project's advisory for a patched version and move to it once it is published.Source: vulncheck.com