Quick answers
- Is CVE-2025-60497 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-60497 being exploited in the wild.
- How severe is CVE-2025-60497?
- 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-60497?
- 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-60497 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-60497?
- 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 null pointer dereference occurs in the GetESD function (isomedia/track.c) when processing a corrupted MP4 sample description (stsd) entry. The code attempts to dereference a null pointer without checking if the pointer is non-null before accessing its members. The fix adds a bounds check (dpnd && dpnd->trackIDCount) to prevent dereferencing a null pointer when processing stream dependencies.
Affected products
- GPAC Project MP4Box before 2.5
Timeline
- 2025-09-09: disclosed
- 2025-09-09: patched: Fix committed to master branch
- 2026-10-21: advisory