Quick answers
- Is CVE-2025-60482 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-60482 being exploited in the wild.
- How severe is CVE-2025-60482?
- Informational severity, published 19 October 2026.
- Which products and versions are affected?
- GPAC Project MP4Box 2.5-DEV-rev1593 and earlier.
- Is there a fix for CVE-2025-60482?
- Yes: fixed in Fixed in commit e02d1fd24cdc26acb1b236ab38b3832cffcae21b (2025-07-15). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-60482 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2025-60482?
- 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: Fixed in commit e02d1fd24cdc26acb1b236ab38b3832cffcae21b (2025-07-15)
Technical details
A heap use-after-free vulnerability exists in the gf_odf_ac4_cfg_clean_list function in odf/descriptors.c, triggered during parsing of specially crafted AC4 audio configuration descriptors. The vulnerability is reachable via local file processing without authentication, with exploitation resulting in process termination via memory corruption.
Affected products
- GPAC Project MP4Box 2.5-DEV-rev1593 and earlier
Timeline
- 2025-10-19: disclosed
- 2025-07-15: patched: Fix committed upstream