Skip to main content
Menu
CVEs

GPAC use-after-free in XMT file parser

MP4Box in GPAC versions up to and including 26.07.0 is affected when it parses a crafted XMT scene file. No fixed version is named; the fix is commit 3e535640b48ed3218e74929cbf3e42250fce3ddf.

CVE-2026-134665Published , updated

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

Summary

GPAC MP4Box has a use-after-free flaw in its XMT scene loader that lets an attacker access freed heap memory by supplying a crafted XMT file, and it can crash MP4Box. The attacker must have local access and a user must open the crafted file.

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 access freed heap memory by supplying a crafted XMT file. When xmt_parse_element() replaces an SFNode field child, the freed node stays cached in parser->peeked_nodes and a later DEF lookup passes it to gf_node_get_name(), crashing MP4Box.

Who should check

Teams running GPAC MP4Box (gpac) 26.07.0 or earlier that parse XMT scene files, including anyone accepting untrusted XMT input.

“Affecting gpac <= 26.07.0”

vulncheck.com

What to do

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

    Affects gpac up to and including 26.07.0 (MP4Box). MP4Box must parse a crafted XMT scene file.
  2. Apply the vendor's patch: 3e535640b48ed3218e74929cbf3e42250fce3ddf.

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-134665 (GPAC MP4Box through 26.07.0 Use-After-Free in gf_node_get_name via XMT Parser), 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-134665 (entry last updated 2026-11-22):
Affected:
- gpac gpac: through 26.07.0
Vendor patches: 3e535640b48ed3218e74929cbf3e42250fce3ddf (source: https://github.com/gpac/gpac/issues/3786). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Affects gpac up to and including 26.07.0 (MP4Box). (source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-use-after-free-in-gf-node-get-name-via-xmt-parser)
- MP4Box must parse a crafted XMT scene file. (source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-use-after-free-in-gf-node-get-name-via-xmt-parser)
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-134665 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134665 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/3e535640b48ed3218e74929cbf3e42250fce3ddf
- https://github.com/gpac/gpac/issues/3786
- https://github.com/gpac/gpac/blob/v26.07.0/src/scene_manager/loader_xmt.c#L2081-L2084
- https://github.com/gpac/gpac/blob/v26.07.0/src/scenegraph/base_scenegraph.c#L1336-L1340
- https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-use-after-free-in-gf-node-get-name-via-xmt-parser
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-134665
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-134665"}.

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 8

Questions about CVE-2026-134665

Is CVE-2026-134665 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?

MP4Box can access heap memory after it has been freed when it parses a crafted XMT file. This use-after-free crashes MP4Box.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134665?

gpac: through 26.07.0.

Source: cve.now feed data

Am I affected, and how do I check?

The affected range is gpac up to and including 26.07.0, and the bug is triggered when MP4Box parses an XMT scene file. Check the installed gpac version against that range to see which version applies to your setup.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134665?

No fixed release is named. The fix is commit 3e535640b48ed3218e74929cbf3e42250fce3ddf, which the advisory says will close the issue once it is merged into the master branch.

Source: vulncheck.com, github.com

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