FFmpeg through 9.0.2 contains an uncontrolled resource consumption vulnerability in parseframeheader() in libavcodec/jpegxlparser.c that…
CVE-2026-125264
FFmpeg through 9.0.2 contains an uncontrolled resource consumption vulnerability in parseframeheader() in libavcodec/jpegxlparser.c that fails to validate TOC entry counts against remaining input. Attackers can supply a crafted JPEG XL frame header with a permuted TOC and huge toccount, making the parser loop excessively and exhaust CPU.
Assessment
- CVSS
- 6.8 (v4.0)
- Severity
- Medium
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 9 November 2026
- Last updated
- 9 November 2026
- Assigner
- VulnCheck
CVSS vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
At the source
References
- https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/25569
- https://github.com/FFmpeg/FFmpeg/commit/bc896c613ec0d4ad0108d62fbdda0196f69e7121
- https://github.com/FFmpeg/FFmpeg/blob/n9.0.2/libavcodec/jpegxl_parser.c#L1343
- https://github.com/FFmpeg/FFmpeg
- https://www.vulncheck.com/advisories/ffmpeg-through-9.0.2-cpu-exhaustion-via-jpeg-xl-parser-toc-count
Community proofs of concept
No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.
Submit a proof of concept
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-125264