Skip to main content
Menu
CVEs

GPAC memory corruption in XMT file parser

Affects GPAC MP4Box through 26.07.0 when it processes a crafted XMT file in which a Conditional node owns an unregistered command. No fixed version is named; the fix is patch 5e620ef.

CVE-2026-134670Published , 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 file handling that writes to freed heap memory. An attacker with local access, without needing to log in, can persuade a user to process a crafted XMT file, corrupting heap memory and crashing MP4Box.

Written by a model

Original description

GPAC MP4Box through 26.07.0 contains a use-after-free vulnerability in xmt_node_end() in src/scene_manager/loader_xmt.c that writes to freed heap memory when replacing single-node field commands. Attackers can persuade users to process a crafted XMT file where a Conditional node owning the command is unregistered, corrupting heap memory and crashing MP4Box.

Who should check

Teams running GPAC MP4Box through 26.07.0 that process XMT files, such as users importing or converting XMT scenes

“GPAC MP4Box through 26.07.0”

vulncheck.com

What to do

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

    Processing a crafted XMT file in which a Conditional node owns the command that is unregistered.
  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-134670 (GPAC MP4Box through 26.07.0 Use-After-Free via xmt_node_end), 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-134670 (entry last updated 2026-11-22):
Affected:
- gpac gpac: through 26.07.0
Vendor patches: 5e620ef (source: https://github.com/gpac/gpac/issues/3776). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Processing a crafted XMT file in which a Conditional node owns the command that is unregistered. (source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-use-after-free-via-xmt-node-end)
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-134670 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134670 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/issues/3776
- https://github.com/gpac/gpac/blob/v26.07.0/src/scene_manager/loader_xmt.c#L3147-L3158
- https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-use-after-free-via-xmt-node-end
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-134670
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-134670"}.

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 7

Questions about CVE-2026-134670

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

Processing a crafted XMT file can trigger a use-after-free in xmt_node_end, corrupting heap memory and crashing MP4Box.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134670?

gpac: through 26.07.0.

Source: cve.now feed data

Am I affected, and how do I check?

MP4Box versions through 26.07.0 are in range. The bug needs a crafted XMT file in which a Conditional node owns a command that is unregistered. Check the installed MP4Box version against 26.07.0 to see whether it falls in that range.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134670?

No fixed version is listed. The fix is patch 5e620ef, which the project closed as completed on Jul 25, 2026.

Source: vulncheck.com, github.com

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