GPAC heap buffer over-read in the XML SAX parser
MP4Box through 26.07.0 is affected when importing a crafted XMT file whose ROUTE or command references a later-defined node. No fixed version is named; the vendor's fix is patch 5e620ef.
- Exploited
- No known exploitation
- Fix
- Vendor patch: 5e620ef
- Who is exposed
- Specific setups only
Summary
GPAC MP4Box through 26.07.0 has a heap buffer over-read in its XML parser that an attacker can use to read memory past a heap line buffer. It is reached locally: an attacker crafts an XMT file that a user must import into MP4Box, and the crash that follows is the visible effect.
Written by a model
Original description
GPAC MP4Box through 26.07.0 contains a heap-based buffer over-read vulnerability in gf_xml_sax_peek_node() in src/utils/xml_parser.c that lets attackers read past the heap line buffer. Attackers can craft an XMT file whose ROUTE or command references a later-defined node, crashing MP4Box when a user imports it.
Who should check
Teams running GPAC MP4Box through 26.07.0 that import XMT scene files, including anyone processing untrusted XMT input.
“GPAC MP4Box through 26.07.0”
What to do
Check whether your setup matches what the bug needs.
The MP4Box import of a crafted XMT file whose ROUTE or command references a later-defined node.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-134669 (GPAC MP4Box through 26.07.0 Heap Buffer Over-read in gf_xml_sax_peek_node), 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-134669 (entry last updated 2026-11-22):
Affected:
- gpac gpac: through 26.07.0
Vendor patches: 5e620ef (source: https://github.com/gpac/gpac/issues/3780). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- The MP4Box import of a crafted XMT file whose ROUTE or command references a later-defined node. (source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-heap-buffer-over-read-in-gf-xml-sax-peek-node)
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-134669 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134669 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/3780
- https://github.com/gpac/gpac/blob/v26.07.0/src/utils/xml_parser.c#L1594-L1598
- https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-heap-buffer-over-read-in-gf-xml-sax-peek-node
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-134669
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-134669"}.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-134669 |
| Record | NVD · CVE-2026-134669 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · sigdevel/pocs · res/gpac/MP4Box/171/171_gf_xml_sax_peek_node_utils_xml_parser_c_1596.xmt |
| Other links 4 | |
| Patch | GitHub · gpac/gpac · Commit 5e620eff |
| Report | GitHub · gpac/gpac · Issue #3780 |
| Repository | GitHub · gpac/gpac · src/utils/xml_parser.c · L1594-L1598 |
| Link | vulncheck.com · advisories/gpac-mp4box-through-26.07.0-heap-buffer-over-read-in-gf-xml-sax-peek-node |
Questions about CVE-2026-134669
Is CVE-2026-134669 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 reads past the end of a heap line buffer while importing a crafted XMT file. The out-of-bounds heap read causes MP4Box to crash.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134669?
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. The bug is triggered by an XMT file whose ROUTE or command references a node defined later in the file. Check your installed MP4Box version against 26.07.0.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134669?
The advisory names no fixed version. The vendor's fix is patch 5e620ef, which GPAC closed as completed on Jul 25, 2026, so apply that patch to your GPAC source.
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-134667GPAC MP4Box through 26.07.0 Stack Buffer Overflow via xmt_resolve_od_links
- CVE-2026-134668GPAC MP4Box through 26.07.0 Use-After-Free in XMT Loader
- 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.