Quick answers
- Is CVE-2025-60491 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-60491 being exploited in the wild.
- How severe is CVE-2025-60491?
- 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-60491?
- Yes: fixed in MP4Box 2.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-60491 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2025-60491?
- 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: MP4Box 2.5
Technical details
The vulnerability is a heap use-after-free in the dasher_flush_segment function within filters/dasher.c. It is triggered when processing crafted MPEG-TS input during DASH segmentation. The flaw allows reading or writing to freed memory, triggered by providing a malicious media file to the MP4Box command-line tool with DASH segmentation enabled.
Affected products
- GPAC Project MP4Box before 2.5
Timeline
- 2025-08-27: disclosed
- 2025-09-09: patched