# CVE-2026-90612: GPAC MP4Box scene_dump.c gf_sm_dump_command_list assertion

> A local attacker can trigger a reachable assertion in GPAC MP4Box, causing a denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-4vjf-m49p-5r5w, UBUNTU-CVE-2026-90612

## What is CVE-2026-90612?

CVE-2026-90612 is a medium-severity denial of service vulnerability in GPAC, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in GPAC up to f1219cde. Affected is the function gf_sm_dump_command_list of the file scene_manager/scene_dump.c of the component MP4Box. The manipulation leads to reachable assertion. The attack must be carried out locally. The exploit is publicly available and might be used. Upgrading to version abi-16.23 is able to address this issue. The identifier of the patch is afca1f1181668d85941d51ed1adf647807d5d975. Upgrading the affected component is advised.

Weakness: CWE-617 (Reachable Assertion)

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


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

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

## Is CVE-2026-90612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90612 is a medium-severity denial of service vulnerability in GPAC, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90612 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-90612/ (Markdown: https://insights.sbomify.com/CVE-2026-90612/index.md)
```

## Sources

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

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