CVE-2026-134670 in MP4Boxinfo

Summary

by MITRE • 11/22/2026

GPAC MP4Box through 26.07.0 contains a use-after-free vulnerability in xmt_node_end() in src/scene_manager/loader_xmt.c that writes to freed heap memory when replacing single-node field commands. Attackers can persuade users to process a crafted XMT file where a Conditional node owning the command is unregistered, corrupting heap memory and crashing MP4Box.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/22/2026

The vulnerability identified in GPAC MP4Box versions up to 26.07.0 represents a critical use-after-free condition located within the scene manager module, specifically inside the xmt_node_end function found in src/scene_manager/loader_xmt.c. This flaw arises during the processing of Extensible Markup Language (XML) based Media Transport files, commonly known as XMT documents. The core technical issue stems from improper memory management when handling field commands associated with single-node structures. When MP4Box processes a crafted XMT file containing specific command sequences, it fails to correctly track the lifecycle of certain node objects in relation to their associated data pointers. This oversight leads to a scenario where memory previously allocated for a node is deallocated or freed by the system while references to that same memory block are still actively maintained and utilized by other parts of the application logic.

The operational mechanism of this exploit relies on the interaction between Conditional nodes and field command replacements. In normal operation, when a single-node field command is replaced, the software must ensure that any existing pointers or handles referencing the old node structure are invalidated before the memory is released. However, in vulnerable versions, if a Conditional node owning the command is unregistered during this process, the application proceeds to free the underlying heap memory associated with that node without clearing all active references. Subsequently, when the xmt_node_end function attempts to finalize or clean up these structures, it accesses the now-dangling pointer. This access results in writing data to a region of heap memory that has already been returned to the operating system for reuse by other processes or internal allocations.

The impact of this vulnerability is primarily characterized by application instability and potential denial of service conditions. When an attacker persuades a user to open a maliciously crafted XMT file, the use-after-free condition triggers immediate corruption of heap memory. This corruption typically manifests as crashes within MP4Box, effectively denying access to media processing capabilities for legitimate users. While modern operating systems employ various mitigations such as Address Space Layout Randomization and Data Execution Prevention which may hinder exploitation, the presence of arbitrary write primitives in a use-after-free scenario significantly increases the risk profile. In more complex attack vectors involving heap grooming techniques, this memory corruption could potentially be leveraged to achieve remote code execution by overwriting function pointers or object vtables with attacker-controlled values, although such an outcome depends heavily on the specific environment and compiler protections enabled at compile time.

From a classification perspective, this vulnerability aligns closely with CWE-416, which defines use-after-free errors where software continues to use memory after it has been freed. It also relates to CWE-787, out-of-bounds write, as the corrupted heap data may overwrite adjacent structures depending on allocation patterns. In terms of adversary tactics, this flaw supports techniques associated with ATT&CK T1203, exploitation for defense evasion or initial access if combined with social engineering, and potentially T1059, command and script interpreter execution if successful code injection occurs through the heap corruption mechanism. The vulnerability highlights a deficiency in reference counting logic within the XMT loader component of GPAC.

Mitigation strategies should focus on immediate software updates to versions where this issue has been patched by the developers. Until an update is available, users are advised to avoid processing untrusted or unknown source XMT files and to restrict the execution privileges of MP4Box processes to limit potential impact from heap corruption events. For developers integrating GPAC into larger systems, implementing strict input validation on incoming media descriptors can help reduce exposure. Furthermore, enabling comprehensive logging for memory allocation failures in development environments can assist in identifying similar logic errors before they reach production deployments. Regular security audits focusing on lifecycle management of dynamically allocated structures within multimedia parsers are recommended to prevent recurrence of such high-severity memory safety issues.

Responsible

VulnCheck

Reservation

11/22/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!