CVE-2026-134671 in MP4Box
Summary
by MITRE • 11/22/2026
GPAC MP4Box through 26.07.0 contains a use-after-free vulnerability in the XMT-A scene loader that allows attackers to corrupt heap memory via crafted XMT files. Attackers can persuade a user to process an XMT file whose discarded out-of-scope nodes cause gf_node_unregister() to dereference a freed child, crashing the process.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/22/2026
The vulnerability identified in GPAC MP4Box versions up to 26.07.0 represents a critical memory safety flaw within the XMT-A scene loader component. This use-after-free condition arises from improper management of object lifecycles during the parsing and processing of Extensible MPEG-4 Textual (XMT) files, specifically those adhering to the XMT-A profile used for 3D content delivery in multimedia containers like MP4. The core technical flaw involves a race-like state where nodes that have been marked as out-of-scope or discarded are not fully nullified from their parent references before being deallocated. Consequently, when subsequent processing steps attempt to unregister these nodes via the gf_node_unregister function, the system dereferences memory addresses that have already been freed by earlier cleanup routines. This results in undefined behavior, typically manifesting as heap corruption rather than a clean crash, which significantly expands the potential attack surface beyond simple denial of service scenarios.
From an operational perspective, this vulnerability allows attackers to craft malicious XMT files designed specifically to trigger these invalid memory accesses when processed by vulnerable instances of MP4Box. The immediate impact includes application instability and crashes, leading to a denial of service for users relying on GPAC tools for media processing or conversion. However, the deeper risk lies in the potential for arbitrary code execution. Heap corruption can be leveraged to overwrite function pointers or other critical data structures within the process memory space. If an attacker can control the contents of the freed heap region through careful crafting of the input file and potentially leveraging allocator behavior, they may achieve remote code execution with the privileges of the user running MP4Box. This is particularly dangerous in environments where automated processing pipelines handle untrusted media files without sufficient sandboxing or validation layers.
This vulnerability aligns closely with Common Weakness Enumeration (CWE) category CWE-416, which describes Use After Free errors. The specific mechanism involves a pointer being used after it has been freed, leading to unpredictable behavior depending on how the memory allocator reuses that space. In the context of modern security frameworks such as MITRE ATT&CK, this flaw facilitates initial access and execution techniques where malicious files are delivered via social engineering or automated ingestion systems. The attacker's ability to corrupt heap memory places them in a position to manipulate control flow within the application, potentially bypassing standard protections if Address Space Layout Randomization (ASLR) is not fully effective against the specific allocation patterns exploited by this bug.
Mitigation strategies for this vulnerability primarily involve updating GPAC MP4Box to version 26.07.1 or later, where the developers have addressed the lifecycle management issues within the XMT-A scene loader. Until an update can be applied, organizations should implement strict input validation and sanitization processes for any XMT files processed by these tools. It is advisable to restrict the use of GPAC utilities in untrusted environments or behind reverse proxies that perform deep packet inspection and file type verification before handing off media assets for processing. Additionally, enabling heap protection mechanisms such as SafeSEH on Windows or using compilers with stack-smashing detection can provide additional layers of defense against exploitation attempts derived from this memory corruption flaw.