Quick answers
- Is CVE-2025-60492 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-60492 being exploited in the wild.
- How severe is CVE-2025-60492?
- 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-60492?
- Yes: fixed in GPAC 2.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-60492 attacked?
- It is attacked with local access.
- Am I affected by CVE-2025-60492?
- 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: GPAC 2.5
Technical details
A stack overflow occurs in the gf_bifs_dec_node function (bifs/field_decode.c) due to uncontrolled recursion when processing specially crafted BIFS scene data within MP4 containers. The vulnerability involves recursive calls between gf_bifs_dec_node, BD_DecMFFieldList, and related functions that exhaust stack memory. An attacker can trigger this by providing a malicious MP4 file to MP4Box, causing immediate denial of service through application crash.
Affected products
- GPAC Project MP4Box before 2.5
Timeline
- 2025-08-13: disclosed
- 2025-09-09: patched