CVE-2026-10201: Assimp UV Channel FBXExporter.cpp WriteObjects divide by zero
A vulnerability was determined in Assimp up to 6.0.4. This vulnerability affects the function FBXExporter::WriteObjects of the file FBXExporter.cpp of the component UV Channel Handler. Executing a manipulation can lead to divide by zero. The attack needs to be launched locally. The exploit has been publicly disclosed and may be utilized. Applying a patch is advised to resolve this issue. The project tagged the reported issue as bug.
Security readout for executives and security teams
Plain-English summary
Assimp versions 6.0.0 through 6.0.4 have a divide-by-zero flaw in FBX export UV-channel handling. The likely business impact is a local crash or processing failure, not data theft. Treat it as moderate priority where Assimp processes untrusted 3D assets or runs in automated content pipelines.
Executive priority
Moderate. This is mainly an availability risk in local or pipeline processing, but public exploit disclosure raises urgency for environments handling untrusted 3D content.
Technical view
CVE-2026-10201 affects FBXExporter::WriteObjects in FBXExporter.cpp, within Assimp's UV Channel Handler. VulDB assigns CVSS 4.0 score 4.8 with local attack vector, low complexity, low privileges, no user interaction, and low availability impact. Sources cite CWE-369 and CWE-404, with public exploit material disclosed.
Likely exposure
Exposure is most likely on developer workstations, build systems, or media pipelines using Assimp 6.0.0-6.0.4 and exercising FBX export on local or user-controlled assets. The sources do not identify downstream products or remote service exposure.
Exploitation context
KEV is false, so there is no cited evidence of active exploitation. The source bundle says exploit material has been publicly disclosed and may be used. Attack requirements are local with low privileges and no user interaction according to the supplied CVSS vector.
Researcher notes
Evidence is limited to the CVE/VulDB description and referenced Assimp issue material. The issue is tagged as a bug, affects the FBX exporter UV-channel path, and has public proof-of-concept material referenced, but sources do not confirm active exploitation or a fixed release number.
Mitigation direction
Inventory Assimp usage and identify versions 6.0.0 through 6.0.4.
Check upstream Assimp guidance, issue 6613, and vendor packaging for the fixed patch.
Prioritize systems processing untrusted or externally supplied 3D assets.
Restrict untrusted FBX export workflows until patched.
Add crash isolation around automated asset conversion jobs.
Validation and detection
Confirm whether applications link against or package Assimp 6.0.0-6.0.4.
Review asset-processing workflows for FBX export usage.
Check dependency manifests, container images, and static builds for bundled Assimp copies.
Monitor vendor advisories for a named fixed release or backported patch.
Verify patched builds no longer include the vulnerable FBXExporter.cpp behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-369: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-369 · source CWE mapping
Divide By Zero
Divide By Zero represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Resource Shutdown or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.