Quick answers
- Is CVE-2026-125245 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125245 being exploited in the wild.
- How severe is CVE-2026-125245?
- Medium severity, with a CVSS score of 4.7, published 9 November 2026.
- Which products and versions are affected?
- Ffmpeg through 9.0.2.
- Is there a fix for CVE-2026-125245?
- Yes: fixed in FFmpeg 9.1 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125245 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-125245?
- 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 and later
Technical details
The vulnerability is a memory leak in ff_mjpeg_decode_sof() in libavcodec/mjpegdec.c where the hwaccel_picture_private pointer is overwritten without freeing the previous allocation. Attackers trigger this by sending MJPEG streams with repeated SOF (Start of Frame) markers or failing frames when hardware acceleration (VAAPI or NVDEC) is active. The leaked memory may contain sensitive hardware buffer data from previous frames.
Affected products
- FFmpeg FFmpeg through 9.0.2
Timeline
- 2026-11-09: disclosed
- 2026-10-27: patched: PR #25231 merged fixing hwaccel decode state issues