# CVE-2026-9572: GPAC MP4Box media.c Media_GetSample memory leak

> A local attacker can trigger a memory leak in GPAC MP4Box, potentially causing 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:** 26 May 2026
- **Updated:** 28 May 2026
- **Also known as:** DEBIAN-CVE-2026-9572, GHSA-77xc-cwff-62wp, UBUNTU-CVE-2026-9572

## What is CVE-2026-9572?

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

### Official description

A security vulnerability has been detected in GPAC up to 2.4.0. Affected by this issue is the function Media_GetSample of the file src/isomedia/media.c of the component MP4Box. Such manipulation of the argument cat leads to memory leak. The attack can only be performed from a local environment. The exploit has been disclosed publicly and may be used. The name of the patch is e79c5cbe8b3fed27f4854ec229457d30c96206f1. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 1 product.


Products: Gpac Gpac.

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

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

## Is CVE-2026-9572 being exploited?

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

## Other vulnerabilities in Gpac Gpac

- [CVE-2023-46427](https://insights.sbomify.com/CVE-2023-46427/): Null dereference in n/a (critical 9.8)
- [CVE-2023-46932](https://insights.sbomify.com/CVE-2023-46932/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-36190](https://insights.sbomify.com/CVE-2022-36190/): Use after free in n/a (critical 9.8)
- [CVE-2021-28300](https://insights.sbomify.com/CVE-2021-28300/): Null dereference in n/a (critical 9.8)
- [CVE-2020-11558](https://insights.sbomify.com/CVE-2020-11558/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9572 is a medium-severity denial of service vulnerability in Gpac Gpac, published on 26 May 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-9572 exists.

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

## Sources

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

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