# CVE-2026-132775: GPAC before 26.07.0 Use-After-Free in gf_node_try_destroy via XMT Field-Replace


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/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-q8ch-8vjv-7f4h, UBUNTU-CVE-2026-132775

## What is CVE-2026-132775?

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

### Official description

GPAC before 26.07.0 contains a use-after-free vulnerability in xmt_node_end() that allows attackers to corrupt memory by attaching nodes from unrelated proto sub-graphs to field-replace commands. Attackers can supply a crafted XMT scene buffering such a command in a Conditional node, causing gf_node_try_destroy() to access the freed node, crashing MP4Box and corrupting the heap.

Weakness: CWE-416 (Use After Free)

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

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-132775?

Upgrade gpac/gpac to 26.07.0 or later.

## Is CVE-2026-132775 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132775 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-132775 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-132775/ (Markdown: https://insights.sbomify.com/CVE-2026-132775/index.md)
```

## Sources

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

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