Quick answers
- Is CVE-2026-120245 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120245 being exploited in the wild.
- How severe is CVE-2026-120245?
- Medium severity, with a CVSS score of 5.5, published 1 November 2026.
- Which products and versions are affected?
- Ffmpeg 0.10 through 9.0.2.
- Is there a fix for CVE-2026-120245?
- Yes: fixed in FFmpeg 9.1 (merged 2026-10-10). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120245 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-120245?
- Check whether you run Ffmpeg at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: FFmpeg 9.1 (merged 2026-10-10)
Technical details
The sunrast_decode_frame() function fails to initialize a temporary bitmap when decoding truncated 1-bit and 4-bit paletted Sun Raster images, leading to uninitialized memory being read and expanded into output pixels. An attacker can craft a malicious truncated Sun Raster file to trigger this condition and cause heap memory leaks such as allocator metadata to appear in the decoded image data.
Affected products
- FFmpeg FFmpeg 0.10 through 9.0.2
Timeline
- 2026-11-01: disclosed: CVE-2026-120245 published
- 2026-10-10: patched: Fix merged in PR #24877