GPAC stack buffer overflow in XMT object descriptor parsing
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Summary
A stack-based buffer overflow in GPAC MP4Box lets an attacker corrupt stack memory and crash the program using a crafted XMT scene file with an over-long object descriptor URL fragment. The attack is local and requires no login, but a user must load the malicious file.
Written by a model
Original description
GPAC MP4Box through 26.07.0 contains a stack-based buffer overflow vulnerability in xmt_resolve_od_links() that allows attackers to corrupt stack memory via over-long object descriptor URL fragments. Attackers can craft an XMT scene file whose URL fragment overflows the fixed 5000-byte szURL buffer via sprintf, crashing MP4Box when a user loads it.
Who should check
Teams running GPAC MP4Box 26.07.0 or earlier, or any pipeline that loads untrusted XMT scene files with MP4Box.
“Affecting gpac <= 26.07.0”
What to do
Check whether your setup matches what the bug needs.
Affects GPAC MP4Box through version 26.07.0. A user loads a crafted XMT scene file whose OD-link URL fragment is over-long.Apply the patch listed under Evidence.
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-134667 (GPAC MP4Box through 26.07.0 Stack Buffer Overflow via xmt_resolve_od_links), 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-134667 (entry last updated 2026-11-22):
Affected:
- gpac gpac: through 26.07.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects GPAC MP4Box through version 26.07.0. (source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-stack-buffer-overflow-via-xmt-resolve-od-links)
- A user loads a crafted XMT scene file whose OD-link URL fragment is over-long. (source: https://github.com/gpac/gpac/issues/3902)
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-134667 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134667 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/5c9990b0f45ef21aa79c7fa79d49b3f3b8e08057
- https://github.com/gpac/gpac/issues/3902
- https://github.com/gpac/gpac/blob/v26.07.0/src/scene_manager/loader_xmt.c#L583-L591
- https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-stack-buffer-overflow-via-xmt-resolve-od-links
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-134667
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-134667"}.Affected versions
- gpac gpacthrough 26.07.0
cve.now Index
- 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
- CVE published
- First seen by cve.now
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134667 |
| Record | NVD · CVE-2026-134667 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · sigdevel/pocs · res/gpac/MP4Box/176/176_xmt_resolve_od_links_scene_manager_loader_xmt_c_602.xmt |
| Other links 4 | |
| Patch | GitHub · gpac/gpac · Commit 5c9990b0 |
| Report | GitHub · gpac/gpac · Issue #3902 |
| Repository | GitHub · gpac/gpac · src/scene_manager/loader_xmt.c · L583-L591 |
| Link | vulncheck.com · advisories/gpac-mp4box-through-26.07.0-stack-buffer-overflow-via-xmt-resolve-od-links |
Questions about CVE-2026-134667
Is CVE-2026-134667 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 crafted XMT scene file with an over-long URL fragment in an object descriptor link makes sprintf write past the end of a stack buffer named szURL. This corrupts stack memory and can crash MP4Box, causing a denial of service.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134667?
gpac: through 26.07.0.
Source: cve.now feed data
Am I affected, and how do I check?
GPAC MP4Box through version 26.07.0 is affected, per the listed range that starts at 0 and ends at 26.07.0. The bug is triggered when MP4Box loads an XMT scene file whose OD-link URL fragment is over-long, so the version reported by MP4Box's version output can be compared with that range.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134667?
No fixed version is listed in the checked facts, so no upgrade target can be named from them. Check the GPAC project's advisory or release notes for a patch before relying on any version.
Source: vulncheck.com, github.com
Related
- CVE-2026-134662GPAC MP4Box through 26.07.0 Double Free via gf_sg_sfcommand_del
- CVE-2026-134663GPAC MP4Box through 26.07.0 Use-After-Free in gf_sg_command_new via XMT Loader
- CVE-2026-134665GPAC MP4Box through 26.07.0 Use-After-Free in gf_node_get_name via XMT Parser
- CVE-2026-134668GPAC MP4Box through 26.07.0 Use-After-Free in XMT Loader
- CVE-2026-134669GPAC MP4Box through 26.07.0 Heap Buffer Over-read in gf_xml_sax_peek_node
- CVE-2026-134670GPAC MP4Box through 26.07.0 Use-After-Free via xmt_node_end
No corrections so far. Something wrong on this page? Report an error.