CVE-2026-125264
Received Received - Intake

Uncontrolled Resource Consumption in FFmpeg JPEG XL Parser

Vulnerability report for CVE-2026-125264, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-09

Last updated on: 2026-11-09

Assigner: VulnCheck

Description

FFmpeg through 9.0.2 contains an uncontrolled resource consumption vulnerability in parse_frame_header() in libavcodec/jpegxl_parser.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 toc_count, making the parser loop excessively and exhaust CPU.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-09
Last Modified
2026-11-09
Generated
2026-11-10
AI Q&A
2026-11-10
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
FFmpeg FFmpeg From 0 (inc) to 9.0.2 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-606 The product does not properly check inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an uncontrolled resource consumption issue in FFmpeg versions up to 9.0.2. It occurs in the JPEG XL parser where the function parse_frame_header() fails to validate the number of TOC (Table of Contents) entries against the remaining input data. Attackers can exploit this by providing a maliciously crafted JPEG XL frame header with a permuted TOC and an excessively high toc_count value. This causes the parser to enter an infinite or excessively long loop, consuming excessive CPU resources.

Detection Guidance

Detecting this vulnerability requires checking for excessive CPU usage during JPEG XL file processing. Monitor system processes for abnormal CPU consumption when handling JPEG XL files. Use tools like 'top', 'htop', or 'ps' to identify processes consuming high CPU. Additionally, inspect network traffic for unusual JPEG XL file transfers.

Impact Analysis

If you use FFmpeg to process JPEG XL files, this vulnerability could allow attackers to cause denial-of-service conditions by consuming all available CPU resources. This may lead to system slowdowns, crashes, or rendering your system unresponsive during file processing.

Compliance Impact

This vulnerability primarily causes CPU exhaustion through excessive parsing loops, which may lead to system unavailability. While not directly violating GDPR or HIPAA, such resource exhaustion could disrupt systems handling personal or health data, potentially violating availability requirements under GDPR Article 32 and HIPAA Security Rule requirements for access control and integrity.

Mitigation Strategies

Immediately update FFmpeg to the latest version that patches this issue. If updating is not possible, disable JPEG XL parsing in FFmpeg by removing or renaming libavcodec/jpegxl_parser.c. Restrict access to systems processing JPEG XL files until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-125264. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...