Quick answers
- Is CVE-2026-90611 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90611 being exploited in the wild.
- How severe is CVE-2026-90611?
- Low severity, with a CVSS score of 3.3, published 14 September 2026.
- Which products and versions are affected?
- Gpac MP4Box up to f1219cde.
- Is there a fix for CVE-2026-90611?
- A patch was published on 2026-07-27: Fix committed (afca1f1); included in version abi-16.23 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-90611 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-90611?
- 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 reachable assertion triggered in the xmt_parse_element function of scene_manager/loader_xmt.c within the MP4Box component. The flaw arises from improper handling of malformed XMT (GPAC's XML-based scene format) input, allowing an attacker to trigger a controlled crash via a crafted file. Attack requires local execution of the affected parsing code. The issue does not permit code execution or privilege escalation, but causes denial of service through application termination. A patch was committed in July 2026 (commit afca1f1) and is included in version abi-16.23 and later.
Affected products
- GPAC MP4Box up to f1219cde
Timeline
- 2026-09-14: disclosed: CVE-2026-90611 published
- 2026-07-27: patched: Fix committed (afca1f1); included in version abi-16.23