# CVE-2026-91091: GPAC Node Insertion base_scenegraph.c gf_node_list_insert_child memory corruption

> Remote attackers can trigger memory corruption in GPAC via crafted content, potentially leading to code execution.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-q5hg-62rj-mq63, UBUNTU-CVE-2026-91091

## What is CVE-2026-91091?

CVE-2026-91091 is a medium-severity memory corruption vulnerability in GPAC, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was identified in GPAC up to f1219cde. The impacted element is the function gf_node_list_insert_child of the file scenegraph/base_scenegraph.c of the component Node Insertion. Such manipulation leads to memory corruption. The attack can be launched remotely. The exploit is publicly available and might be used. Upgrading to version abi-16.23 is sufficient to resolve this issue. The name of the patch is 49dee5cad329cfed310c1682703df7daa47df31a. It is suggested to upgrade the affected component.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-91091 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91091 is a medium-severity memory corruption vulnerability in GPAC, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91091 exists.

Affected product: GPAC. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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