Is there a public PoC exploit available for CVE-2026-10199?

Yes, a public proof-of-concept exploit is available for CVE-2026-10199. Prioritise patching immediately. EPSS: 0.0%.

Is there a patch available for CVE-2026-10199?

Yes, a patch is available for CVE-2026-10199. Update the affected software to the latest version immediately.

Assimp CVE-2026-10199

Q: What is the CVSS score of CVE-2026-10199?

CVE-2026-10199 has a CVSS 4.0 base score of 1.9 (Low). CVSS 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-33521 LOW

NULL Pointer Dereference (CWE-476)

2026-05-31 VulDB

GHSA-6rfw-vrjc-wff7

Denial Of Service Null Pointer Dereference Assimp N A

1.9

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

1.9 LOW

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

CVSS changed

May 31, 2026 - 23:22 NVD

3.3 (LOW) 1.9 (LOW)

Source Code Evidence Fetched

May 31, 2026 - 23:16 vuln.today

Analysis Generated

May 31, 2026 - 23:16 vuln.today

DescriptionCVE.org

A vulnerability has been found in Assimp up to 6.0.4. Affected by this issue is the function glTF2::LazyDict in the library glTF2Asset.h. Such manipulation of the argument operator[] leads to null pointer dereference. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. The name of the patch is d24b85319bd70c65883a2b96613e07e23fb95981. It is best practice to apply a patch to resolve this issue.

AnalysisAI

Null pointer dereference in Assimp's glTF2 importer (versions up to 6.0.4) allows a local low-privileged attacker to crash any application that processes attacker-supplied 3D model files via the library. The flaw resides in the ImportAnimations() function, where glTF2::LazyDict::operator[] is invoked with animation channel node indices that are never validated for validity before dereferencing, producing a CWE-476 null pointer dereference and denial-of-service. A public proof-of-concept exploit (poc.zip) has been disclosed and an upstream patch commit is available, though no active exploitation is confirmed by CISA KEV.

Technical ContextAI

Assimp (Open Asset Import Library) is a widely-used C++ library for importing and converting 3D model formats. Its glTF2 importer uses a templated LazyDict<T> container in glTF2Asset.h to lazily resolve indexed assets. In glTF2Importer.cpp, the ImportAnimations() function iterates animation channel target mappings and previously accessed nodes directly via r.nodes[iter.first] - the LazyDict::operator[] overload - without checking whether the returned reference is valid. A crafted glTF2 file embedding animation channels with out-of-bounds or nonexistent node indices causes operator[] to return a null or invalid reference, which is subsequently dereferenced by CreateNodeAnim() or CreateMeshMorphAnim(), triggering a crash. The root cause is CWE-476 (NULL Pointer Dereference), stemming from absent input validation on foreign-key-style references within the glTF2 asset graph.

RemediationAI

The upstream fix is available as commit d24b85319bd70c65883a2b96613e07e23fb95981, delivered through pull request #6646 at https://github.com/assimp/assimp/pull/6646. Users should rebuild Assimp from source incorporating this commit or await an official tagged release that includes it - a specific patched release version number is not confirmed from the available data, so users must verify against official Assimp release tags at https://github.com/assimp/assimp/releases. As a compensating control where patching is not immediately feasible, applications should validate or strip glTF2 animation channel node references prior to passing files to Assimp, using a schema-level validator such as the glTF-Validator tool (note: this adds processing overhead and may not catch all malformed cases). Additionally, sandboxing or process-isolating the Assimp import step (e.g., via a worker process with restricted privileges) limits crash impact to that subprocess and prevents disruption of the parent application.