# CVE-2025-60468: Use after free in n/a

> A local attacker can cause a denial of service by processing a crafted media file, triggering a heap use-after-free in GPAC MP4Box.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** DEBIAN-CVE-2025-60468, GHSA-fj4j-92hj-mcwp, UBUNTU-CVE-2025-60468

## What is CVE-2025-60468?

CVE-2025-60468 is a medium-severity use after free vulnerability in Gpac Gpac, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GPAC Multimedia Open Source Project GPAC Project/MP4Box 2.5-DEV-rev1593-gfe88c3545-master is affected by: Buffer Overflow. The impact is: cause a denial of service (local). The component is: filter_core/filter_pid.c (L:574-580): function gf_filter_pid_inst_swap_delete_task() improperly accesses freed objects during PID instance swap/delete cleanup, leading to heap use-after-free. The attack vector is: Local (AV:L): a local, authenticated user who processes a specially crafted MPEG-2 TS/MP4 file with MP4Box can trigger the bug during filter teardown (PID instance swap/delete), causing a crash. ¶¶ In GPAC s MP4Box, gf_filter_pid_inst_swap_delete_task() in filter_core/filter_pid.c may dereference objects after they have been freed when cleaning up PID instances after a swap/delete operation. Crafted inputs (e.g., malformed MPEG-2 TS) can trigger a heap use-after-free and crash; exploitation may be possible.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-60468?

It affects 1 product.


Products: Gpac Gpac.

## How do I fix CVE-2025-60468?

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

## Is CVE-2025-60468 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60468 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-2025-60468 and fix it if it is affected.

What it is: CVE-2025-60468 is a medium-severity use after free vulnerability in Gpac Gpac, published on 24 Jun 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-2025-60468 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-2025-60468/ (Markdown: https://insights.sbomify.com/CVE-2025-60468/index.md)
```

## Sources

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

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