A flaw has been found in Assimp up to 6.0.4. Affected by this vulnerability is the function Assimp::glTFImporter::ImportMeshes of the file glTFImporter.cpp of the component glTFImporter. This manipulation causes null pointer dereference. The attack is restricted to local execution. The exploit has been published and may be used. 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 can crash when its glTF importer reaches a null pointer condition in ImportMeshes. The source describes local execution only, so business impact is primarily denial of service in workstations, tools, or pipelines that process glTF assets with Assimp.
Executive priority
Handle as a moderate availability risk, not an emergency remote-code-execution event. Prioritize teams that process external 3D assets or rely on Assimp in automated workflows, because public proof-of-concept material is referenced.
Technical view
CVE-2026-10198 affects Assimp glTFImporter.cpp, function Assimp::glTFImporter::ImportMeshes. VulDB reports a null pointer dereference classified under CWE-476 and CWE-404. CVSS 4.0 is 4.8 with local attack vector, low complexity, low privileges, no user interaction, and low availability impact.
Likely exposure
Exposure is likely where Assimp 6.0.0-6.0.4 is used to import glTF assets. The bundle does not establish remote exposure, but asset-processing services, build pipelines, desktop applications, or security tools using affected Assimp builds should be reviewed.
Exploitation context
The bundle says an exploit has been published and may be used, and includes a GitHub attachment tagged exploit. KEV is false, and the provided sources do not state active exploitation in the wild.
Researcher notes
Evidence is limited to the CVE/VulDB record and upstream issue references in the bundle. No vendor fix version, patch note, or active exploitation confirmation is provided. Validate reachability before escalating, because the CVSS vector is local and availability-only.
Mitigation direction
Inventory applications and pipelines using Assimp 6.0.0 through 6.0.4.
Check Assimp issue 6609 and vendor guidance for fixed release information.
Avoid processing untrusted glTF assets until remediation guidance is confirmed.
Run asset-import workflows with least privilege and isolation where practical.
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-404: 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-404 · source CWE mapping
Improper Resource Shutdown or Release
Improper Resource Shutdown or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.