FFmpeg through 9.0.2 FLIC Decoder Out-of-Bounds Write via FLI_BRUN Byte Swap
- 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. Target is a big-endian build of FFmpeg Input is a 15/16 bpp FLIC/FLX file containing an FLI_BRUN chunk
- 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 an out-of-bounds write vulnerability in flic_decode_frame_15_16BPP() in libavcodec/flicvideo.c that allows attackers to corrupt heap memory on big-endian builds. Attackers can supply a crafted 15/16 bpp FLIC/FLX file with an FLI_BRUN chunk whose non-terminating byte-swap loop writes packet-derived data past the frame buffer, crashing the process.
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.
Target is a big-endian build of FFmpeg Input is a 15/16 bpp FLIC/FLX file containing an FLI_BRUN chunkApply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- FFmpeg FFmpeg
through 9.0.2
Evidence 7
- Patch
- Patch
- Patch
- Report
- Repository
Show all 7 sourcesShow fewer sources
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125181
Is CVE-2026-125181 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 in FFmpeg writes packet-derived data past the end of the frame buffer when it handles an FLI_BRUN chunk. A crafted file can corrupt heap memory and crash the process.Source: vulncheck.com
Which versions are affected by CVE-2026-125181?
FFmpeg: through 9.0.2.Source: cve.now feed data
Am I affected, and how do I check?
Affects FFmpeg builds up to and including 9.0.2, but only when the build is big-endian and the input is a 15 or 16 bpp FLIC/FLX file containing an FLI_BRUN chunk. To check your build's byte order, look at the target architecture used to compile FFmpeg; the version can be seen with ffmpeg -version.Source: vulncheck.com
How do I fix CVE-2026-125181?
No fixed version is listed in the checked facts, so no upgrade target can be named from them. Watch the FFmpeg project for a release that includes the fix.Source: vulncheck.com