Quick answers
- Is CVE-2026-125264 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125264 being exploited in the wild.
- How severe is CVE-2026-125264?
- Medium severity, with a CVSS score of 5.5, published 9 November 2026.
- Which products and versions are affected?
- Ffmpeg through 9.0.2.
- Is there a fix for CVE-2026-125264?
- 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-125264 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-125264?
- 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
An uncontrolled resource consumption vulnerability exists in parse_frame_header() in libavcodec/jpegxl_parser.c, where the parser fails to validate TOC (table of contents) entry counts against the amount of remaining input data. An attacker can craft a JPEG XL frame header with a permuted TOC and oversized toc_count value, causing the parser to loop excessively and exhaust CPU. The vulnerability is triggered by processing malformed JPEG XL image files and requires no authentication or user interaction beyond opening the file.
Affected products
- FFmpeg FFmpeg through 9.0.2
Timeline
- 2026-11-09: disclosed
- 2026-11-03: patched: Merged in PR #25569