Quick answers
- Is CVE-2025-55667 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-55667 being exploited in the wild.
- How severe is CVE-2025-55667?
- Informational severity, published 19 October 2026.
- Which products and versions are affected?
- Gpac MP4Box 2.5-DEV-rev1672-gc9a31d0e1-master and earlier.
- Is there a fix for CVE-2025-55667?
- Yes: fixed in GPAC MP4Box after commit e6d01820d7bf3967d931fedb379ee5f209bc133b. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-55667 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2025-55667?
- 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 MP4Box after commit e6d01820d7bf3967d931fedb379ee5f209bc133b
Technical details
The dump_isom_saps function in filedump.c fails to validate track metadata pointers before dereferencing them when analyzing Sync Access Point (SAP) information. When processing MP4 files with missing or corrupted Sample Description Box (stsd) entries, the function attempts to read from invalid memory locations. An attacker can trigger this via a malformed MP4 file, resulting in a denial of service.
Affected products
- GPAC MP4Box 2.5-DEV-rev1672-gc9a31d0e1-master and earlier
Timeline
- 2025-08-05: disclosed
- 2025-08-05: patched: Fixed in commit e6d0182