Skip to main content
Menu
CVEs

GPAC heap corruption in XMT-A scene loader

Only affects gpac MP4Box up to and including 26.07.0 when an XMT scene file has malformed nesting inside a Conditional node's command buffer. The fix is commit 5e620ef.

CVE-2026-134662Published , updated

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

Summary

Written by a model

GPAC MP4Box through 26.07.0 contains a double free vulnerability in the XMT-A scene loader that leaves a stale GF_Command pointer in a Conditional node's SFCommandBuffer when the buffer element is not properly closed. Attackers can persuade users to process a crafted XMT file with malformed nesting, causing gf_sg_sfcommand_del() to free the live command, corrupting heap memory and crashing the process.

Who should check

Teams running GPAC MP4Box up to 26.07.0 that load XMT-A scene files, such as media pipelines or converters handling 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 MP4Box up to and including 26.07.0 XMT-A scene file with malformed nesting inside a Conditional node's command buffer The buffer element in the XMT file is not properly closed
  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-134662 (GPAC MP4Box through 26.07.0 Double Free via gf_sg_sfcommand_del), 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-134662 (entry last updated 2026-11-22):
Affected:
- gpac gpac: through 26.07.0
Vendor patches: 5e620ef (source: https://github.com/gpac/gpac/issues/3767). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Affects gpac MP4Box up to and including 26.07.0 (source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-double-free-via-gf-sg-sfcommand-del)
- XMT-A scene file with malformed nesting inside a Conditional node's command buffer (source: https://github.com/gpac/gpac/issues/3767)
- The buffer element in the XMT file is not properly closed (source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-double-free-via-gf-sg-sfcommand-del)
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-134662 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134662 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/commit/6fc2832ba83467bbf89349395e89de1353ab5b77
- https://github.com/gpac/gpac/issues/3767
- https://github.com/gpac/gpac/issues/3766
- https://github.com/gpac/gpac/issues/3773
- https://github.com/gpac/gpac/issues/3774
- https://github.com/gpac/gpac/issues/3788
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-134662
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-134662"}.

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 18

Questions about CVE-2026-134662

Is CVE-2026-134662 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 double free in MP4Box corrupts heap memory and crashes the process when it parses a crafted XMT scene file with malformed nesting inside a Conditional node's command buffer, where the buffer element is not properly closed.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134662?

gpac: through 26.07.0.

Source: cve.now feed data

Am I affected, and how do I check?

gpac MP4Box up to and including 26.07.0 is in the affected range. The trigger is an XMT scene file whose buffer element is not properly closed. To check a installation, compare the installed gpac version number against 26.07.0.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134662?

The fix is commit 5e620ef, which the advisory records as completed. The facts name no fixed release version, so use a gpac build that includes that commit.

Source: vulncheck.com, github.com

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