Quick answers
- Is CVE-2026-90686 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90686 being exploited in the wild.
- How severe is CVE-2026-90686?
- Medium severity, with a CVSS score of 5.3, published 14 September 2026.
- Which products and versions are affected?
- Gpac MP4Box up to f1219cde.
- Is there a fix for CVE-2026-90686?
- A patch was published on 2026-07-27: Fix commit afca1f1181668d85941d51ed1adf647807d5d975 available Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-90686 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-90686?
- 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
The vulnerability is a function call with incorrect number of arguments (CWE-685) in the gf_bt_report() function within scene_manager/loader_bt.c. When parsing a malformed BT/BIFS command, gf_bt_parse_bifs_command() passes a format string with %s conversion specifier to gf_bt_report() without providing the corresponding string argument. This missing variadic argument causes vsnprintf() to read from an invalid memory location, triggering an invalid memory read. The attack vector is remote—any application processing attacker-controlled BT/BIFS files through MP4Box is affected. A patch (commit afca1f1181668d85941d51ed1adf647807d5d975) corrects the variadic call by supplying the missing argument. The fix is available in version abi-16.23 and later.
Affected products
- GPAC MP4Box up to f1219cde
Timeline
- 2026-09-14: disclosed: CVE-2026-90686 published
- 2026-07-27: patched: Fix commit afca1f1181668d85941d51ed1adf647807d5d975 available