FFmpeg through 9.0.2 Heap Buffer Overflow via cbs_jpeg_write_scan Integer Overflow
Only 32-bit builds of FFmpeg through 9.0.2 are affected, and only when a JPEG/MJPEG scan of 512 MiB or more is processed by CBS bitstream filters such as filter_units. The facts give no vendor rating or fix.
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. Affects 32-bit builds of FFmpeg through 9.0.2 A JPEG/MJPEG scan of 512 MiB or more must be supplied The stream must be processed by CBS bitstream filters such as filter_units
- 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 integer overflow in cbs_jpeg_write_scan() in libavcodec/cbs_jpeg.c that causes a heap buffer overflow on 32-bit builds. Attackers can supply a crafted MJPEG/JPEG stream with a scan of 512 MiB or more, processed by CBS bitstream filters like filter_units, to corrupt the heap or crash the application.
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.
Affects 32-bit builds of FFmpeg through 9.0.2 A JPEG/MJPEG scan of 512 MiB or more must be supplied The stream must be processed by CBS bitstream filters such as filter_unitsApply 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-125227
Is CVE-2026-125227 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?
A JPEG or MJPEG stream with a scan of 512 MiB or more, processed by CBS bitstream filters such as filter_units, causes a heap buffer overflow. The overflow can corrupt the heap or crash the application.Source: vulncheck.com
Which versions are affected by CVE-2026-125227?
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 in the affected range, and the flaw is stated to affect 32-bit builds. Check your FFmpeg version and whether your build is 32-bit to see whether the range applies to your installation.Source: vulncheck.com
How do I fix CVE-2026-125227?
The checked facts name no fixed version, so no upgrade target can be given from them. Consult the FFmpeg project's advisory for a fix or workaround.Source: vulncheck.com