# CVE-2026-10201: Assimp divide by zero in FBXExporter

Source: https://junglewise.ai/threats/cve-2026-10201-assimp-divide-by-zero-in-fbxexporter  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-01. Updated: 2026-06-01  
License: CC BY 4.0 with a link back

CVE-2026-10201 · Severity: low · CVSS 3.3 · Published 2026-06-01

Assimp is a widely used library for importing and exporting 3D model files. A vulnerability in its FBX export component can cause the software to crash when processing a specially crafted 3D model. This could lead to a denial-of-service, interrupting workflows for users or automated systems that process 3D assets.

Technologies: [Assimp](https://junglewise.ai/threats/technologies/assimp). Vendors: [Assimp](https://junglewise.ai/threats/vendors/assimp).

## 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

## References

- [https://github.com/assimp/assimp/](https://github.com/assimp/assimp/)
- [https://github.com/assimp/assimp/issues/6613](https://github.com/assimp/assimp/issues/6613)
- [https://github.com/user-attachments/files/27153727/poc.zip](https://github.com/user-attachments/files/27153727/poc.zip)
- [https://vuldb.com/cve/CVE-2026-10201](https://vuldb.com/cve/CVE-2026-10201)
- [https://vuldb.com/submit/821182](https://vuldb.com/submit/821182)
- [https://vuldb.com/vuln/367481](https://vuldb.com/vuln/367481)
- [https://vuldb.com/vuln/367481/cti](https://vuldb.com/vuln/367481/cti)

## Related threats

- [Assimp NULL pointer dereference in Ogre3D importer](https://junglewise.ai/threats/cve-2026-111128-assimp-through-6-0-5-contains-a-null-pointer-dereference)
- [Assimp out-of-bounds read in PLY file handler](https://junglewise.ai/threats/cve-2026-108573-a-vulnerability-was-detected-in-open-asset-import-library-assimp)
- [Assimp MDLImporter heap-based buffer overflow in AddBonesToNodeGraph](https://junglewise.ai/threats/cve-2026-19970-assimp-mdlimporter-heap-based-buffer-overflow-in)
- [Assimp MDL importer heap buffer overflow](https://junglewise.ai/threats/cve-2026-19969-assimp-mdl-importer-heap-buffer-overflow)
- [Assimp heap buffer overflow in LWO2 model parser](https://junglewise.ai/threats/cve-2026-19968-assimp-heap-buffer-overflow-in-lwo2-model-parser)