CVE-2026-134662 in MP4Boxinfo

Summary

by MITRE • 11/22/2026

GPAC MP4Box through 26.07.0 contains a double free vulnerability in the XMT-A scene loader that leaves a stale GF_Command pointer in a Conditional node's SFCommandBuffer when the buffer element is not properly closed. Attackers can persuade users to process a crafted XMT file with malformed nesting, causing gf_sg_sfcommand_del() to free the live command, corrupting heap memory and crashing the process.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/22/2026

The vulnerability identified in GPAC MP4Box versions up through 26.07.0 represents a critical memory management flaw within the XMT-A scene loader component. This specific issue is classified as a double free vulnerability, which occurs when an application attempts to deallocate the same block of memory more than once without proper reinitialization or nullification of pointers in between operations. In this context, the defect resides in how the software handles Conditional nodes and their associated SFCommandBuffer elements during the parsing of XMT files. When a crafted file contains malformed nesting structures where buffer elements are not properly closed according to expected syntax rules, the internal logic fails to maintain consistent state regarding command pointers. This failure results in a stale GF_Command pointer remaining within the conditional node's data structure after an initial deallocation has occurred.

From a technical perspective, the core of this flaw lies in the interaction between the file parser and the scene graph management system. When MP4Box processes an XMT-A file with deeply nested or incorrectly terminated elements, it triggers a sequence where gf_sg_sfcommand_del is invoked to release resources associated with command buffers. Due to the malformed input, the application does not correctly track which pointers have already been freed. Consequently, subsequent processing steps may attempt to access or free these same memory addresses again. This double free condition leads directly to heap corruption because the underlying memory allocator becomes confused by duplicate deallocation requests for the same block. The integrity of the heap data structures is compromised, creating an unstable execution environment that can lead to immediate application termination or unpredictable behavior depending on how the corrupted memory is subsequently utilized.

The operational impact of this vulnerability primarily manifests as a denial of service condition triggered by processing maliciously crafted media files. An attacker who can persuade a user to open or process a specially constructed XMT file with malformed nesting can cause the MP4Box application to crash due to the resulting heap corruption. While modern operating systems employ various mitigations such as Address Space Layout Randomization and stack canaries, these do not necessarily prevent crashes caused by double free errors in all scenarios. The immediate effect is the disruption of service for users relying on GPAC tools for media processing tasks. Furthermore, although the primary observed impact is a crash, heap corruption vulnerabilities are historically significant because they can sometimes be leveraged to achieve arbitrary code execution if an attacker can carefully control the memory layout and subsequent allocations following the double free event.

This vulnerability aligns with Common Weakness Enumeration identifier CWE-415, which describes Double Free conditions that lead to undefined behavior or crashes. It also relates closely to CWE-787, as the out-of-bounds write resulting from heap corruption can overwrite adjacent memory structures. In terms of attack vectors and tactics, this flaw is relevant to MITRE ATT&CK technique T1203, which covers Exploitation for Client Execution, where attackers use malicious files to trigger vulnerabilities in client-side applications like media players or converters. The vulnerability highlights the importance of robust input validation and state management within parsers that handle complex hierarchical data structures such as XMT-A scenes.

To mitigate this risk, users should ensure they are running versions of GPAC MP4Box released after 26.07.0 where this issue has been addressed by developers through improved pointer handling and stricter validation of file structure integrity. Developers integrating or maintaining similar parsers should implement rigorous checks to ensure that pointers are set to null immediately following deallocation operations, preventing subsequent accidental frees. Additionally, employing memory safety tools during development and testing phases can help identify such logic errors before they reach production environments. For end-users, the primary defense remains avoiding the processing of untrusted media files from unknown sources until software updates have been applied.

Responsible

VulnCheck

Reservation

11/22/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!