Quick answers
- Is CVE-2026-125258 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125258 being exploited in the wild.
- How severe is CVE-2026-125258?
- 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-125258?
- 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-125258 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-125258?
- 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
The vulnerability is a division-by-zero in dovi_configure_ext() in libavcodec/dovi_rpuenc.c triggered by an unvalidated zero frame rate denominator. An attacker supplies a crafted HEVC or AV1 input with a nonzero numerator and zero denominator to the dovi_rpu bitstream filter or encoders (libx265, libaom, libsvtav1), causing process termination. The fix validates the denominator before division.
Affected products
- FFmpeg FFmpeg through 9.0.2
Timeline
- 2026-11-09: disclosed: CVE-2026-125258 published
- 2026-11-06: patched: Fix merged in PR #25408