Quick answers
- Is CVE-2026-125244 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125244 being exploited in the wild.
- How severe is CVE-2026-125244?
- High severity, with a CVSS score of 7.8, published 9 November 2026.
- Which products and versions are affected?
- Ffmpeg before 8.1.3 and 9.x before 9.0.2.
- Is there a fix for CVE-2026-125244?
- Yes: fixed in FFmpeg 8.1.3, 9.0.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125244 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-125244?
- 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 8.1.3, 9.0.2
Technical details
The vulnerability is an out-of-bounds write in the VVC decoder's sh_entry_points() function in libavcodec/vvc/ps.c. A maliciously crafted VVC bitstream with specific tile and WPP (Wavefront Parallel Processing) layout parameters can cause the entry_point_start_ctu array to be written beyond its bounds (4,050 elements). The issue occurs during slice header parsing before the decoder validates the entry point count, allowing an attacker to supply excess entry points via network or file-based attack vectors without requiring authentication or user interaction.
Affected products
- FFmpeg FFmpeg before 8.1.3 and 9.x before 9.0.2
Timeline
- 2026-11-09: disclosed
- 2026-09-17: patched