CVE-2026-134681 in MP4Boxinfo

Summary

by MITRE • 11/22/2026

GPAC MP4Box through 26.07.0 contains an uncontrolled recursion vulnerability in gf_sg_proto_instantiate() in src/scenegraph/vrml_proto.c that lacks cycle detection or depth limits. Attackers can craft an XMT scene whose PROTO body instantiates itself directly or indirectly, exhausting the stack and crashing MP4Box when imported.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/22/2026

The vulnerability identified in GPAC MP4Box versions up to 26.07.0 represents a critical failure in input validation within the VRML protocol instantiation logic. Specifically, the function gf_sg_proto_instantiate located in src/scenegraph/vrml_proto.c fails to implement necessary safeguards against recursive calls during the processing of XMT scene files. This architectural oversight allows an attacker to construct maliciously crafted XML-based 3D models where a PROTO definition contains references that lead back to its own instantiation, either directly or through a chain of indirect dependencies. The absence of cycle detection mechanisms means the parser does not recognize when it is re-entering the same logical context, while the lack of depth limits ensures there is no cap on how many times this recursion can occur before the system intervenes.

From a technical perspective, this flaw constitutes an uncontrolled resource consumption vulnerability driven by stack exhaustion. When MP4Box processes such a crafted file, it enters an infinite or excessively deep recursive loop as it attempts to resolve and instantiate the self-referencing PROTO definitions. Each recursive call consumes additional memory on the application's execution stack. Since there is no mechanism to track visited nodes or limit recursion depth, the stack space is rapidly depleted. This leads directly to a stack overflow condition, which typically results in an immediate crash of the MP4Box process. The vulnerability does not require elevated privileges to exploit and can be triggered simply by opening or importing the malicious file within the application interface.

The operational impact of this vulnerability centers on denial of service against users who utilize GPAC MP4Box for media processing tasks involving VRML or XMT formats. An attacker can remotely trigger a crash in the victim's local instance of the software, effectively rendering it unusable until restarted. While the primary manifestation is a crash, stack overflows can sometimes lead to undefined behavior that might be exploitable for code execution depending on compiler protections and memory layout, although the description emphasizes resource exhaustion as the immediate consequence. This affects any workflow where MP4Box is used to parse or convert 3D scene data, including automated pipelines in content creation studios or media processing services that accept user-uploaded assets without sufficient sanitization.

This vulnerability aligns with CWE-675, which describes operations on uncontrolled resources, specifically highlighting the failure to limit recursion depth. It also maps closely to ATT&CK technique T1496, Resource Hijacking, where an adversary uses computational resources such as CPU or memory for their own benefit, in this case causing a denial of service through resource exhaustion. The root cause is classified under CWE-835, Loop with Unreachable Exit Condition Infinite Recursion, indicating that the code logic fails to break out of recursive calls due to missing boundary checks.

Mitigation strategies should focus on both immediate patching and long-term architectural improvements. Users are advised to upgrade GPAC MP4Box to version 26.07.1 or later where this issue has been addressed by implementing proper cycle detection algorithms and recursion depth limits within the gf_sg_proto_instantiate function. For environments unable to update immediately, input validation at the ingestion point is critical; any XMT files should be scanned for suspicious PROTO structures that reference themselves before being passed to MP4Box. Additionally, deploying sandboxing or containerization around media processing tools can limit the blast radius of such crashes, ensuring that a single malformed file does not compromise the entire host system. Security teams should also monitor logs for repeated crash reports associated with VRML parsing operations as an indicator of potential exploitation attempts.

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!