# CVE-2026-130798: GPAC before 26.07.0 Use-After-Free in xmt_resolve_od_links via Discarded XMT Nodes


- **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:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-q3qx-hmx2-qh4c, UBUNTU-CVE-2026-130798

## What is CVE-2026-130798?

CVE-2026-130798 is a medium-severity vulnerability in gpac, published on 17 Nov 2026. 

### Official description

GPAC before 26.07.0 contains a use-after-free vulnerability in the XMT scene loader that leaves dangling MFURL pointers when xmt_node_end() discards nodes. Attackers can convince a user to open a crafted XMT file with MP4Box, causing xmt_resolve_od_links() to access freed heap memory and crash the process.

Weakness: CWE-416 (Use After Free)

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

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

Upgrade gpac/gpac to 26.07.0 or later.

## Is CVE-2026-130798 being exploited?

There is no known exploitation of CVE-2026-130798 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130798 is a medium-severity vulnerability in gpac, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130798 in the wild and no public exploit code.

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

## Sources

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

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