# CVE-2026-90686: GPAC MP4Box loader_bt.c gf_bt_report memory corruption

> Remote attackers can trigger memory corruption in GPAC MP4Box via crafted files, potentially leading to code execution or crashes.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-qwm3-v6mj-w6g3, UBUNTU-CVE-2026-90686

## What is CVE-2026-90686?

CVE-2026-90686 is a medium-severity memory corruption vulnerability in GPAC, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in GPAC up to f1219cde. This affects the function gf_bt_report of the file scene_manager/loader_bt.c of the component MP4Box. The manipulation results in memory corruption. The attack may be performed from remote. The exploit has been made public and could be used. Upgrading to version abi-16.23 is able to mitigate this issue. The patch is identified as afca1f1181668d85941d51ed1adf647807d5d975. 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-90686?


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

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

## Is CVE-2026-90686 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90686 is a medium-severity memory corruption vulnerability in GPAC, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90686 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-90686/ (Markdown: https://insights.sbomify.com/CVE-2026-90686/index.md)
```

## Sources

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

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