Security readout for executives and security teams
Plain-English summary
Assimp, a 3D asset import library, can crash in vulnerable versions when local low-privileged access reaches the affected glTF2 LazyDict code path. The documented impact is limited availability loss, not data theft or code execution. Treat it as a stability and service-resilience issue where Assimp processes untrusted or user-supplied assets.
Executive priority
Prioritize remediation for systems that import untrusted 3D assets or run Assimp in shared processing environments. This is not currently evidenced as actively exploited or code-execution capable, but public exploit disclosure raises urgency for exposed asset-processing workflows.
Technical view
CVE-2026-10199 is a null pointer dereference in glTF2::LazyDict in glTF2Asset.h, triggered through operator[] argument handling. Sources list Assimp 6.0.0 through 6.0.4 as affected, with CWE-404 and CWE-476. CVSS 4.0 is 4.8, local attack vector, low complexity, low privileges, and low vulnerable-system availability impact.
Likely exposure
Exposure is most likely in applications, pipelines, or services embedding Assimp 6.0.0-6.0.4 and processing local or user-controlled glTF assets. Systems not using Assimp, not using affected versions, or not allowing untrusted asset processing have lower exposure.
Exploitation context
The bundle says exploitation is local and that exploit details have been publicly disclosed. KEV is false, and no cited source establishes active exploitation in the wild. The expected outcome is a crash or availability degradation, not confirmed confidentiality or integrity compromise.
Researcher notes
The record is narrow: affected function, versions, CVSS vector, public disclosure, and patch commit are identified. Available evidence supports denial of service via null dereference only. Do not infer remote reachability unless a specific product exposes Assimp processing to remote file submission.
Mitigation direction
- Upgrade or patch Assimp using vendor guidance and commit d24b85319bd70c65883a2b96613e07e23fb95981.
- Identify applications and build dependencies embedding Assimp 6.0.0 through 6.0.4.
- Restrict processing of untrusted glTF assets until patched.
- Isolate asset-conversion jobs from critical services where practical.
- Monitor upstream Assimp issue and pull request status for release guidance.
Validation and detection
- Confirm deployed Assimp versions in packages, source builds, containers, and bundled applications.
- Check whether glTF processing is reachable by local users or user-supplied files.
- Verify the patch commit or an upstream fixed release is present.
- Run existing unit and regression tests for asset import workflows after updating.
- Review crash logs for unexplained Assimp glTF processing failures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCWE-476: 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.
Open ATT&CK lookupCVE-2026-10199 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
4 official scoresWe 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.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P——VulDBCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C1.81.4VulDBCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C1.81.4VulDBAV:L/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:OF/RC:C3.12.9VulDBVulnerability scoring details
Base CVSS 4.0 score
4.8MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
3.3LowVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C
Base CVSS 3.0 score
3.3LowVector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C
Base CVSS 2.0 score
1.7LowVector: AV:L/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:OF/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineVulDB
VulDB entry last update
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- VDB-367479 | Assimp glTF2Asset.h LazyDict null pointer dereferenceCVE reference, VulDB · vdb-entry, technical-description
- VDB-367479 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- CVE-2026-10199 | CVE Analysis and ReportCVE reference, VulDB · third-party-advisory
- Submit #821179 | Assimp commit 17c12da NULL Pointer DereferenceCVE reference, VulDB · third-party-advisory
- https://github.com/assimp/assimp/issues/6611CVE reference, VulDB · issue-tracking
- https://github.com/assimp/assimp/pull/6646CVE reference, VulDB · issue-tracking, patch
- https://github.com/user-attachments/files/27194148/poc.zipCVE reference, VulDB · exploit
- https://github.com/assimp/assimp/commit/d24b85319bd70c65883a2b96613e07e23fb95981CVE reference, VulDB · patch
- https://github.com/assimp/assimp/CVE reference, VulDB · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.