FFmpeg 2.3 through 9.0.2 Huffyuv Decoder Uninitialized Heap Memory Disclosure
Affects FFmpeg 2.3 through 9.0.2 when decoding Huffyuv input that ends before a row is fully decoded. No vendor rating or fixed version is given in the checked facts.
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 open-source multimedia library, is affected in its Huffyuv video decoder. An attacker can craft a malicious Huffyuv video file that causes the decoder to leak uninitialized heap memory into the decoded image, potentially exposing sensitive data from the program's memory.
Read the original description
FFmpeg 2.3 through 9.0.2 contains a use of uninitialized resource vulnerability in the Huffyuv decoder that allows attackers to leak heap memory into decoded pixels via short packed-BGR bitstreams. Attackers can craft a Huffyuv BGR24/BGRA video whose entropy data ends early, causing decode_slice() to add uninitialized s->temp[0] bytes into output frames, exposing heap contents.
What to do
Check whether your setup matches what the bug needs.
Huffyuv bitstream ends before the row is fully decoded (truncated or short input)Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- FFmpeg FFmpeg
From 2.3 · 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-120247
What does this mean?
When Huffyuv input ends early, the decoder does not zero the rest of the row's scratch buffers. Uninitialized memory can then end up in the decoded output.Source: github.com, code.ffmpeg.org
Am I affected, and how do I check?
FFmpeg versions 2.3 through 9.0.2 are in the affected range. The bug needs Huffyuv decoding of truncated or short input, and you can check your version with the command ffmpeg -version.Source: github.com, code.ffmpeg.org
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be given. Check the FFmpeg project's advisory for a fixed release.Source: github.com, code.ffmpeg.org
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