# CVE-2025-60467: A use-after-free in the gf_filter_pid_inst_swap_delete_task function (/filter_core/filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allow


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 27 Oct 2026
- **Also known as:** DEBIAN-CVE-2025-60467, GHSA-3q4w-vhww-wccf, UBUNTU-CVE-2025-60467

## What is CVE-2025-60467?

CVE-2025-60467 is a high-severity vulnerability in Gpac Gpac, published on 24 Jun 2026. 

### Official description

A use-after-free in the gf_filter_pid_inst_swap_delete_task function (/filter_core/filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted media file.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Gpac Gpac.

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

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

## Is CVE-2025-60467 being exploited?

There is no known exploitation of CVE-2025-60467 in the wild and no public exploit code.

## 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-60467 and fix it if it is affected.

What it is: CVE-2025-60467 is a high-severity vulnerability in Gpac Gpac, published on 24 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2025-60467 in the wild and no public exploit code.

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-60467/ (Markdown: https://insights.sbomify.com/CVE-2025-60467/index.md)
```

## Sources

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

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