FFmpeg 0.10 through 9.0.2 Uninitialized Memory Disclosure via Sun Raster Decoder
Affects FFmpeg 0.10 through 9.0.2 when decoding Sun Raster images, specifically the byte-encoded RLE path when input ends early and 1-bit or 4-bit paletted images expanded into PAL8 output.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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
- Fix
- Fix or patch referenced
- 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, the widely used multimedia framework, is affected, and an attacker who supplies a specially crafted, truncated Sun Raster image can cause it to reveal leftover contents of its memory in the decoded output. This is an information disclosure issue that could expose sensitive data from the program's memory.
Read the original description
FFmpeg 0.10 through 9.0.2 contains a use of uninitialized resource vulnerability in sunrast_decode_frame() that leaks heap memory when decoding truncated 1-bit and 4-bit paletted Sun Raster images. Attackers can craft a truncated Sun Raster file so the uncleared temporary bitmap is expanded into PAL8 pixels, exposing stale heap contents such as allocator words in decoded output.
What to do
Check whether your setup matches what the bug needs.
Affects the byte-encoded (RLE) Sun Raster decoding path when the input ends early Affects 1-bit and 4-bit paletted images expanded into PAL8 output Regression introduced by FFmpeg commit ceb0dd9f1eApply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- FFmpeg FFmpeg
From 0.10 · through 9.0.2
Evidence 6
- Patch
- 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-120245
What does this mean?
The Sun Raster decoder can leave uninitialized memory in decoded output, which is a use of uninitialized memory. The issue was found during triage of a security report and reproduced through the API with Valgrind.Source: code.ffmpeg.org, github.com
Am I affected, and how do I check?
FFmpeg versions 0.10 through 9.0.2 are listed as affected. The issue involves Sun Raster decoding, either the byte-encoded RLE path when the input ends early or 1-bit and 4-bit paletted images expanded into PAL8 output. To check a version, run ffmpeg -version.Source: code.ffmpeg.org, github.com
What should I do about it?
The checked facts do not name a fixed version, so no specific upgrade target can be given from them. Check the FFmpeg project's advisory or release notes for a fixed release.Source: code.ffmpeg.org, github.com
Is it 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