# CVE-2026-90824: GPAC MP4Box dom_events.c gf_sg_dom_event_bubble stack-based overflow

> A local attacker can exploit a stack-based buffer overflow in GPAC's MP4Box component to execute arbitrary code or cause 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:** 15 Sep 2026
- **Also known as:** GHSA-78j3-rj3r-98vc, UBUNTU-CVE-2026-90824

## What is CVE-2026-90824?

CVE-2026-90824 is a medium-severity memory corruption 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 has been found in GPAC 26.07.0. Affected is the function gf_sg_dom_event_bubble of the file src/scenegraph/dom_events.c of the component MP4Box. The manipulation leads to stack-based buffer overflow. The attack can only be performed from a local environment. The exploit has been disclosed to the public and may be used. Upgrading to version abi-16.23 is able to address this issue. The identifier of the patch is 9eb40df4448b88d6a6ce3454657c06f47eff0b24. It is recommended to upgrade the affected component.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-90824 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90824 is a medium-severity memory corruption 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-90824 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-90824/ (Markdown: https://insights.sbomify.com/CVE-2026-90824/index.md)
```

## Sources

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

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