Quick answers
- Is CVE-2026-10201 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10201 being exploited in the wild.
- How severe is CVE-2026-10201?
- Low severity, with a CVSS score of 3.3, published 1 June 2026.
- Which products and versions are affected?
- Assimp up to 6.0.4.
- Is there a fix for CVE-2026-10201?
- 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-2026-10201 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-10201?
- Check whether you run Assimp 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 division-by-zero vulnerability (CWE-369) exists in Assimp up to version 6.0.4 within the FBXExporter::WriteObjects function in FBXExporter.cpp. The issue is triggered when the UV Channel Handler encounters a UV channel that exists but contains zero components. An attacker with local access can exploit this by providing a manipulated 3D model for export, leading to an application crash (denial of service). A proof-of-concept has been publicly disclosed, and the issue is tracked by the project as a bug in the FBX export logic.
Affected products
- Assimp Assimp up to 6.0.4
Timeline
- 2026-04-28: disclosed: Issue reported on GitHub repository
- 2026-06-01: advisory: CVE published