Quick answers
- Is CVE-2026-125265 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125265 being exploited in the wild.
- How severe is CVE-2026-125265?
- Medium severity, with a CVSS score of 5.3, published 9 November 2026.
- Which products and versions are affected?
- Ffmpeg through 9.0.2.
- Is there a fix for CVE-2026-125265?
- Yes: fixed in FFmpeg 9.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125265 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-125265?
- 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
Technical details
A use-after-free flaw exists in libavcodec/nvdec.c where the ff_nvdec_start_frame() function fails to reset the bitstream pointer (ctx->bitstr) when handling slice errors, allowing a subsequent picture decode to reuse freed heap memory. An attacker can craft malicious video with incomplete frames that abandon processing before end_frame is called, causing cuvidDecodePicture() to read from freed memory, leading to information disclosure or denial of service.
Affected products
- FFmpeg FFmpeg through 9.0.2
Timeline
- 2026-11-09: disclosed
- 2026-10-27: patched