Quick answers
- Is CVE-2026-125249 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125249 being exploited in the wild.
- How severe is CVE-2026-125249?
- High severity, with a CVSS score of 7, published 9 November 2026.
- Which products and versions are affected?
- Ffmpeg 7.1 through 9.0.2.
- Is there a fix for CVE-2026-125249?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-125249 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-125249?
- 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.
Technical details
The vulnerability is an integer overflow in ff_vk_decode_add_slice() in libavcodec/vulkan_decode.c that miscalculates the Vulkan hwaccel bitstream buffer size. An attacker can craft a video stream with over 2 GiB of slice data per frame, causing memcpy() to write past a smaller pooled host-mapped buffer, resulting in a heap buffer overflow. The defect affects Vulkan-accelerated video decoding when processing malicious input streams.
Affected products
- FFmpeg FFmpeg 7.1 through 9.0.2
Timeline
- 2026-11-09: disclosed