Skip to main content
Menu
CVEs

GPAC use-after-free in XMT scene loader

CVE-2026-134668Published , updated

6.9MediumCNA
Exploited
No known exploitation
Fix
Vendor patch: 5e620ef
Who is exposed
Specific setups only

Summary

GPAC MP4Box contains a use-after-free flaw in its XMT scene loader that lets a local attacker corrupt heap memory and crash the tool. The attacker needs no login, but a user must open a crafted XMT file for the attack to work.

Written by a model

Original description

GPAC MP4Box through 26.07.0 contains a use-after-free vulnerability in the XMT scene loader that allows attackers to corrupt heap memory when xmt_node_end() discards an out-of-scope node without resetting command-buffer state. Attackers can supply a crafted XMT file that leaves parser->command_buffer and parser->command dangling, causing later parsing to access freed memory and crash MP4Box.

Who should check

Teams running GPAC MP4Box 26.07.0 or earlier that load XMT scene files, including anyone parsing untrusted XMT input.

“Affecting gpac <= 26.07.0”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affected GPAC MP4Box versions up to and including 26.07.0 A crafted XMT scene file is parsed by MP4Box
  2. Apply the vendor's patch: 5e620ef.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134668 (GPAC MP4Box through 26.07.0 Use-After-Free in XMT Loader), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134668 (entry last updated 2026-11-22):
Affected:
- gpac gpac: through 26.07.0
Vendor patches: 5e620ef (source: https://github.com/gpac/gpac/issues/3782). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Affected GPAC MP4Box versions up to and including 26.07.0 (source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-use-after-free-in-xmt-loader)
- A crafted XMT scene file is parsed by MP4Box (source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-use-after-free-in-xmt-loader)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-134668 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134668 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/gpac/gpac/commit/5e620eff3bea16972dd948b2a153e416ffb1c81d
- https://github.com/gpac/gpac/commit/3e535640b48ed3218e74929cbf3e42250fce3ddf
- https://github.com/gpac/gpac/issues/3782
- https://github.com/gpac/gpac/issues/3781
- https://github.com/gpac/gpac/issues/3789
- https://github.com/gpac/gpac/issues/3790
- https://github.com/gpac/gpac/issues/3775
- https://github.com/gpac/gpac/blob/v26.07.0/src/scene_manager/loader_xmt.c#L3193-L3197
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134668
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134668"}.

Affected versions

cve.now Index

12Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 16

Questions about CVE-2026-134668

Is CVE-2026-134668 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A use-after-free bug in MP4Box's XMT loader lets a crafted XMT scene file corrupt heap memory. The result is that MP4Box can crash.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134668?

gpac: through 26.07.0.

Source: cve.now feed data

Am I affected, and how do I check?

GPAC MP4Box versions up to and including 26.07.0 are affected when they parse an XMT scene file. To check a version, run MP4Box with its version option and compare the output against 26.07.0.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134668?

The fix is GPAC commit 5e620ef, which the project closed as completed on Jul 25, 2026. No released version is named as the fix, so apply that commit or check the GPAC repository for a release that includes it.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.