Quick answers
- Is CVE-2025-60479 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-60479 being exploited in the wild.
- How severe is CVE-2025-60479?
- 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-60479?
- 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-60479 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-60479?
- 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
A NULL pointer dereference exists in the StatSFVec2f function in scene_manager/scene_stats.c when processing MPEG-4 BIFS scenes with malformed vector fields. The vulnerability occurs when the statistics collection code fails to validate pointer integrity before accessing SFVec2f structures. An attacker can trigger a segmentation fault by supplying a crafted MPEG-4 file; the fix validates pointers before dereferencing them.
Affected products
- GPAC Project MP4Box before 2.5
Timeline
- 2025-08-07: disclosed: Vulnerability reported via GitHub issue #3322
- 2025-08-07: patched: Fixed in commit 75786eb