Quick answers
- Is CVE-2026-125269 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125269 being exploited in the wild.
- How severe is CVE-2026-125269?
- High severity, with a CVSS score of 7, published 9 November 2026.
- Which products and versions are affected?
- Ffmpeg through 9.0.2.
- Is there a fix for CVE-2026-125269?
- 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-125269 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-125269?
- 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 double-free vulnerability exists in libavcodec/cbs_sei.c where cbs_sei_delete_message() fails to clear the extension_data reference that ff_cbs_sei_add_message() later reuses. An attacker can craft an H.264 bitstream containing a display orientation SEI message with payload extension data, processed by h264_metadata with display_orientation=insert, to corrupt the heap and potentially achieve arbitrary code execution.
Affected products
- FFmpeg FFmpeg through 9.0.2
Timeline
- 2026-11-09: disclosed
- 2026-11-05: patched: Fix merged via PR #25020