Quick answers
- Is CVE-2025-55653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-55653 being exploited in the wild.
- How severe is CVE-2025-55653?
- Informational severity, published 16 October 2026.
- Which products and versions are affected?
- Gpac MP4Box v2.4 and earlier.
- Is there a fix for CVE-2025-55653?
- Yes: fixed in GPAC commit 4bbb6e5 (post-v2.4). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-55653 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2025-55653?
- 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.
How to fix
- Fixed in: GPAC commit 4bbb6e5 (post-v2.4)
Technical details
The gf_parse_lfrac function in utils/error.c performs division on a denominator without validating it is non-zero, leading to a SIGFPE when processing MP4 files containing zero-denominator fraction strings. This is a denial-of-service vulnerability triggered by providing a malicious MP4 file to MP4Box, requiring no authentication or user interaction beyond opening the file.
Affected products
- GPAC MP4Box v2.4 and earlier
Timeline
- 2025-05-31: disclosed: Issue reported on GitHub
- 2025-06-10: patched: Fix committed as 4bbb6e5