# CVE-2026-128240: GPAC through 26.07.0 Use-After-Free in gf_sg_proto_del During Scene Teardown


- **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:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-ffqp-3677-6hc6, UBUNTU-CVE-2026-128240

## What is CVE-2026-128240?

CVE-2026-128240 is a medium-severity vulnerability in gpac, published on 13 Nov 2026. 

### Official description

GPAC through 26.07.0 contains a use-after-free vulnerability in gf_sg_proto_del() in src/scenegraph/vrml_proto.c because gf_sg_reset() frees unregistered prototypes still referenced by scene commands. Attackers can supply a crafted XMT/BT scene declaring prototypes via commands, processed by MP4Box -chap, to trigger freed memory access and crash the process.

Weakness: CWE-416 (Use After Free)

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

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

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

## Is CVE-2026-128240 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128240 is a medium-severity vulnerability in gpac, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-128240 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-128240/ (Markdown: https://insights.sbomify.com/CVE-2026-128240/index.md)
```

## Sources

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

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