CVE-2026-134696 in MP4Box
Summary
by MITRE • 11/22/2026
GPAC MP4Box through 26.07.0 contains a use-after-free vulnerability in gf_sg_proto_del that allows attackers to free PROTOs still owned by another scene command via the GF_SG_PROTO_DELETE handler. Attackers can craft an XMT scene that declares a PROTO in one command and deletes it by ID in another, crashing MP4Box and corrupting heap memory when opened.
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 within GPAC MP4Box versions up to 26.07.0 represents a critical use-after-free condition located specifically within the gf_sg_proto_del function. This flaw stems from an improper management of object lifecycles in the scene graph handling logic, where memory allocated for PROTO definitions is not correctly tracked against their active references by other commands. When MP4Box processes an XMT scene file that contains a specific sequence of operations, it fails to verify whether a PROTO node being deleted is still actively referenced or owned by another part of the scene structure. This lack of reference counting validation allows the application to proceed with freeing memory blocks that are simultaneously in use elsewhere in the program's execution flow, leading directly to heap corruption and potential code execution scenarios if exploited maliciously.
From a technical perspective, the core issue lies in the GF_SG_PROTO_DELETE handler which processes deletion requests based on identifier rather than comprehensive dependency analysis. An attacker can craft an XMT scene file that first declares a PROTO node within one command block, thereby establishing its presence and potential usage in the scene graph. Subsequently, another command in the same file issues a delete operation targeting this specific PROTO by its unique ID. Because MP4Box does not adequately check if other active commands or nodes still hold references to this PROTO instance before executing the free operation, it releases the underlying memory while that data remains accessible through existing pointers. This creates a classic use-after-free state where subsequent access to the freed memory results in undefined behavior, typically manifesting as application crashes due to segmentation faults or more severe consequences such as arbitrary code execution if an attacker can control the content written into the reclaimed heap space.
The operational impact of this vulnerability is significant for users relying on MP4Box for media processing and scene validation tasks. The immediate consequence observed during exploitation is a denial of service, characterized by the abrupt termination of the application when opening or parsing the crafted malicious file. However, beyond simple crashes, the corruption of heap memory poses a severe security risk. Heap corruption can lead to data leakage, privilege escalation, or remote code execution depending on the specific architecture and how the freed memory is reallocated for other purposes within the process. This makes MP4Box particularly vulnerable when used in automated pipelines that ingest untrusted media files from external sources without rigorous sanitization prior to processing.
This vulnerability aligns with Common Weakness Enumeration CWE-416, which describes use-after-free errors resulting from improper memory management practices. In terms of attack vector classification under the MITRE ATT&CK framework, this flaw facilitates initial access and potentially privilege escalation through exploitation of software vulnerabilities in media parsers or converters. The ability to crash a widely used tool like MP4Box also impacts availability, mapping to techniques that disrupt service continuity. To mitigate these risks, organizations should immediately update GPAC MP4Box to versions newer than 26.07.0 where the reference counting logic has been corrected to prevent deletion of active nodes. Additionally, implementing strict input validation and sandboxing for any tool processing untrusted XMT or MP4 files can reduce the attack surface by isolating potential exploitation attempts from critical system resources.