# CVE-2026-132768: GPAC before 26.07.0 Use-After-Free in xmt_find_node via XMT Peeked Nodes


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-7532-jxh4-57jh, UBUNTU-CVE-2026-132768

## What is CVE-2026-132768?

CVE-2026-132768 is a medium-severity vulnerability in gpac, published on 18 Nov 2026. 

### Official description

GPAC MP4Box before 26.07.0 contains a use-after-free vulnerability in xmt_find_node() in loader_xmt.c that leaves freed forward-referenced nodes cached in parser->peeked_nodes. Attackers can supply a crafted XMT file with a node targeted by an SFCommandBuffer command, triggering a later DEF lookup on the freed node and crashing MP4Box.

Weakness: CWE-416 (Use After Free)

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

1 open source package ship an affected version, including gpac/gpac.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `gpac/gpac` | GitHub | `pkg:github/gpac/gpac` | All versions | 26.07.0 |

## How do I fix CVE-2026-132768?

Upgrade gpac/gpac to 26.07.0 or later.

## Is CVE-2026-132768 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132768 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132768 and fix it if it is affected.

What it is: CVE-2026-132768 is a medium-severity vulnerability in gpac, published on 18 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132768 exists.

Affected packages and fixed versions:
- gpac/gpac (GitHub): affected all versions; fixed in 26.07.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132768/ (Markdown: https://insights.sbomify.com/CVE-2026-132768/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132768
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132768
- OSV: https://osv.dev/vulnerability/CVE-2026-132768

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132768/
Summaries are generated and may contain mistakes; the official description above is the record.
