CVE-2026-134690 in MP4Box
Summary
by MITRE • 11/22/2026
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability that allows attackers to crash the application by supplying a crafted XMT scene. Attackers can modify InputSensor, Layout or EnvironmentTest nodes during parsing, triggering compositor handlers that read uninitialized private stacks and cause denial of service.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/22/2026
The vulnerability identified in GPAC MP4Box versions up through 26.07.0 represents a critical stability issue rooted in improper input validation within the multimedia processing engine. Specifically, this flaw manifests as a NULL pointer dereference when the application processes crafted XMT scene files. The core of the technical failure lies in how the parser handles specific nodes such as InputSensor, Layout, and EnvironmentTest during the parsing phase. When an attacker supplies a maliciously constructed file containing these elements with malformed or missing data structures, the internal logic fails to verify that required pointers are properly initialized before they are accessed by compositor handlers. This oversight leads directly to the application attempting to read from uninitialized private stacks or null memory addresses, resulting in an immediate crash of the MP4Box process.
From a technical perspective, this vulnerability is classified under CWE-476, which denotes NULL Pointer Dereference. The attack vector relies on the ability to inject specific XML-based scene descriptions that exploit gaps in error handling routines. During the parsing operation, the software expects certain data structures to be present and valid based on standard XMT specifications. However, when these expectations are not met due to crafted input, the execution flow proceeds without adequate safeguards. The compositor handlers, which are responsible for rendering or processing scene elements, attempt to access memory locations that have not been allocated or initialized. This results in a segmentation fault or similar exception that terminates the application abruptly.
The operational impact of this vulnerability is primarily focused on availability rather than confidentiality or integrity. An attacker who can trick a user into opening a specially crafted XMT file via MP4Box will cause the application to crash, leading to a denial of service condition. In scenarios where GPAC is used as part of an automated pipeline for media processing or transcoding services, such crashes could disrupt workflows and require manual intervention to restart processes. While this specific flaw does not appear to allow for arbitrary code execution due to its nature as a NULL pointer dereference causing a crash rather than memory corruption exploitable for shellcode injection, it remains significant in environments where the reliability of media processing tools is paramount.
To mitigate this risk, users should immediately upgrade GPAC MP4Box to version 26.07.1 or later, where these input validation checks have been strengthened. Until an update can be applied, organizations relying on automated scripts involving untrusted XMT files should implement sandboxing techniques to isolate the processing environment from critical system resources. Additionally, implementing strict file type verification and sanitization of inputs before they reach the parser can reduce exposure. Security teams monitoring for this vulnerability may look for indicators such as unexpected process terminations or core dumps associated with MP4Box when handling XMT files, aligning detection efforts with ATT&CK techniques related to resource hijacking or denial of service via application crashes.