CVE-2026-134667
Deferred Deferred - Pending Action

Stack-Based Buffer Overflow in GPAC MP4Box

Vulnerability report for CVE-2026-134667, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-22

Last updated on: 2026-11-22

Assigner: VulnCheck

Description

GPAC MP4Box through 26.07.0 contains a stack-based buffer overflow vulnerability in xmt_resolve_od_links() that allows attackers to corrupt stack memory via over-long object descriptor URL fragments. Attackers can craft an XMT scene file whose URL fragment overflows the fixed 5000-byte szURL buffer via sprintf, crashing MP4Box when a user loads it.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-22
Last Modified
2026-11-22
Generated
2026-11-22
AI Q&A
2026-11-22
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
gpac gpac From 0 (inc) to 26.7.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-121 A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a stack-based buffer overflow in GPAC MP4Box through version 26.07.0. It occurs in the xmt_resolve_od_links() function when processing XMT scene files with overly long object descriptor URL fragments. The function uses a fixed 5000-byte stack buffer (szURL) and sprintf to construct URLs, which can overflow if the fragment exceeds the buffer size. This corrupts stack memory and may crash MP4Box when loading malicious files.

Detection Guidance

To detect this vulnerability, monitor for crashes in MP4Box when processing XMT files. Use AddressSanitizer (ASan) builds of GPAC to detect stack-buffer-overflow errors. Check for malformed XMT files with excessively long URL fragments (e.g., >5000 bytes) in logs or inputs.

Impact Analysis

An attacker could exploit this by tricking a user into opening a specially crafted XMT file. This could crash MP4Box, corrupt data, or potentially allow arbitrary code execution on the victim's system. The impact depends on the user's privileges and system configuration.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling unauthorized memory corruption through crafted XMT files. If exploited, it may lead to crashes or unexpected behavior in GPAC MP4Box, which could disrupt processing of multimedia content containing sensitive data. However, direct evidence of compliance impact is not provided in the given context.

Mitigation Strategies

Update GPAC to the latest patched version where the fixed buffer is replaced with a dynamically allocated heap buffer. Avoid processing untrusted XMT files. If updating is not possible, restrict access to MP4Box or use ASan-enabled builds to catch overflows.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-134667. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...