CVE-2026-134691 in MP4Boxinfo

Summary

by MITRE • 11/22/2026

GPAC MP4Box through 26.07.0 contains a heap use-after-free vulnerability in gf_event_target_get_node() because destroyed node event targets remain in media object lists. Attackers can supply a crafted XMT scene with nodes such as InputSensor to trigger freed memory reads during gf_scene_disconnect(), crashing the process or corrupting heap memory.

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 within GPAC MP4Box versions up to 26.07.0 represents a critical heap-based use-after-free flaw located specifically in the gf_event_target_get_node function. This issue stems from improper lifecycle management of event target nodes, particularly those associated with InputSensor objects within XMT scene files. When an application processes these media objects, it maintains internal lists to track active targets for event handling purposes. However, during the cleanup or disconnection phase managed by gf_scene_disconnect, the system fails to properly remove references to destroyed node events from these persistent data structures. Consequently, pointers to memory that has already been deallocated remain valid within the list context, creating a dangling pointer scenario where subsequent operations may attempt to access this freed memory region.

From a technical perspective, the root cause lies in the disconnect between object destruction and reference cleanup. When an InputSensor node is destroyed, its associated event target should be immediately purged from all tracking lists to prevent stale references. The absence of this synchronization allows attackers who supply crafted XMT scene files containing specific malformed or maliciously structured nodes to exploit this timing gap. By triggering the disconnection process while these invalid pointers are still referenced in memory structures, an attacker can force the application to read from heap memory that has been returned to the allocator and potentially reused for other purposes. This leads to a classic use-after-free condition where the integrity of the data being read is entirely dependent on what else has allocated that same block of memory since its release.

The operational impact of this vulnerability is severe, primarily manifesting as application instability through process crashes due to segmentation faults or illegal memory access violations. Beyond simple denial of service, heap corruption poses a significant risk for arbitrary code execution if an attacker can carefully control the contents written into the freed memory block before it is reallocated and read by the vulnerable function. This aligns with Common Weakness Enumeration CWE-416, which defines use-after-free errors as conditions where software continues to use pointers that point to deallocated memory. Such flaws are particularly dangerous in media parsing libraries because they often run with elevated privileges or handle untrusted input from various sources, increasing the attack surface for remote exploitation via maliciously crafted multimedia files distributed through email attachments, web downloads, or streaming services.

In terms of threat modeling and detection frameworks, this vulnerability maps to MITRE ATT&CK technique T1203, which covers Exploitation for Client Execution, as attackers would typically rely on tricking a user into opening the malicious XMT file with MP4Box-based software. It also relates to CWE-787, out-of-bounds read, since accessing freed memory can result in reading data outside of intended bounds if the heap layout is manipulated appropriately. Security practitioners should prioritize patching GPAC installations immediately upon upgrading past version 26.07.0 or applying vendor-provided hotfixes that address the event target cleanup logic. Mitigation strategies also include implementing strict input validation for XMT scene files, sandboxing media processing applications to limit potential damage from heap corruption, and deploying memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Heap Protection features in modern operating systems to mitigate exploitation success rates even if the vulnerability is present.

Responsible

VulnCheck

Reservation

11/22/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!