Quick answers
- Is CVE-2025-60478 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-60478 being exploited in the wild.
- How severe is CVE-2025-60478?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- GPAC Project MP4Box before 2.5.
- Is there a fix for CVE-2025-60478?
- Yes: fixed in 2.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-60478 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2025-60478?
- Check whether you run GPAC Project MP4Box at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.5
Technical details
A use-after-free flaw exists in the gf_filter_packet_destroy function (filter_core/filter_pck.c:678) triggered when processing MPEG-2 TS files with malformed PMT/PAT tables and empty DASH segments. The vulnerability stems from improper packet memory lifetime management in the filter pipeline. The fix verifies the nb_shared_packets_out counter before destroying filters to prevent freeing packets that are still in use.
Affected products
- GPAC Project MP4Box before 2.5
Timeline
- 2025-07-16: disclosed
- 2025-07-18: patched