# CVE-2026-132765: GPAC MP4Box through 26.07.0 Use-After-Free in gf_node_try_destroy via Conditional Command


- **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-gmg6-rv8r-m9ch, UBUNTU-CVE-2026-132765

## What is CVE-2026-132765?

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

### Official description

GPAC MP4Box through 26.07.0 contains a use-after-free vulnerability in gf_node_try_destroy because Conditional node commands keep raw pointers to target nodes freed by gf_sg_reset(). Attackers can supply a crafted XMT scene processed with -info or -add to trigger heap use-after-free, crashing the process and corrupting heap memory.

Weakness: CWE-416 (Use After Free)

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

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 to 26.07.0 | None |

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

No fix has been published for CVE-2026-132765 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-132765 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132765 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-132765 exists.

Affected packages and fixed versions:
- gpac/gpac (GitHub): affected all versions up to 26.07.0; no fix listed

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

## Sources

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

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