CVE-2025-60478 A use-after-free in the gf_filter_packet_destroy function (/filter_core/filter_pck.c) of GPAC Project/MP4Box before 2.5 allows attackers to
Medium 5.5
Published
Updated
Check this codebase for CVE-2025-60478 and fix it if it is affected.
What it is: CVE-2025-60478 is a medium-severity vulnerability in n/a, published on 21 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60478 exists.
Affected product: n/a. 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-60478/ (Markdown: https://insights.sbomify.com/CVE-2025-60478/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-60478?
CVE-2025-60478 is a medium-severity vulnerability in n/a, published on 21 Oct 2026.
Official description
A use-after-free in the gf_filter_packet_destroy function (/filter_core/filter_pck.c) of GPAC Project/MP4Box before 2.5 allows attackers to cause a Denial of Service (DoS) via supplying a crafted MPEG-2 file.
Weakness: CWE-416
Which versions are affected by CVE-2025-60478?
How do I fix CVE-2025-60478?
No fix has been published for CVE-2025-60478 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-60478 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60478 exists.
Sources
Also known as GHSA-295m-xjww-3ppw, UBUNTU-CVE-2025-60478.