Quick answers
- Is CVE-2025-55660 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-55660 being exploited in the wild.
- How severe is CVE-2025-55660?
- Informational severity, published 15 June 2026.
- Which products and versions are affected?
- Gpac MP4Box 2.4.
- Is there a fix for CVE-2025-55660?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-55660 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2025-55660?
- Check whether you run Gpac 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.
Technical details
A stack-based buffer overflow exists in GPAC MP4Box v2.4 within the gf_opus_read_length function located in media_tools/av_parsers.c. The vulnerability is triggered when the parser processes a specially crafted MP4 file containing Opus audio metadata with an invalid length field. An attacker can exploit this by providing a malicious file to the utility, leading to a stack exhaustion or corruption that results in an application crash (Denial of Service). This is a local attack vector requiring the victim to open or process the malicious file using the affected MP4Box version.
Affected products
- GPAC MP4Box 2.4
Timeline
- 2026-06-15: disclosed
- 2026-06-15: advisory