FFmpeg through 9.0.2 Heap Buffer Overflow via FLIC Decoder check_pixel_ptr
FFmpeg 9.0.2 and earlier are affected when the FLIC decoder handles frames with negative stride. The checked facts name no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- 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 9.0.2 and earlier are affected Frames with negative stride (the FLIC decoder's bounds check covers only one bound)
- 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 libavcodec/flicvideo.c that allows attackers to write out of bounds because check_pixel_ptr() checks only one bound with negative-stride frames. Attackers can supply a crafted FLIC file whose RLE and delta chunks write pixel data past frame storage, corrupting heap memory to crash applications or possibly execute code.
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 9.0.2 and earlier are affected Frames with negative stride (the FLIC decoder's bounds check covers only one bound)Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- FFmpeg FFmpeg
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-125241
Is CVE-2026-125241 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 FLIC decoder's bounds check covers only one bound when frames have negative stride, so writes can go outside a heap buffer. This corrupts heap memory, which can crash applications or possibly execute code.Source: vulncheck.com
Which versions are affected by CVE-2026-125241?
FFmpeg: through 9.0.2.Source: cve.now feed data
Am I affected, and how do I check?
FFmpeg versions through 9.0.2 are listed as affected. The setup involved is decoding FLIC content with negative-stride frames. To check a installed build's version, run ffmpeg -version.Source: vulncheck.com
How do I fix CVE-2026-125241?
The checked facts name no fixed version, so no upgrade target is known from them. Check FFmpeg's release notes or the advisory for a release newer than 9.0.2.Source: vulncheck.com