CVE-2026-10198
Deferred Deferred - Pending Action
Heap-based Null Pointer Dereference in Assimp glTFImporter

Publication date: 2026-05-31

Last updated on: 2026-05-31

Assigner: VulDB

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-31
Last Modified
2026-05-31
Generated
2026-06-21
AI Q&A
2026-06-01
EPSS Evaluated
2026-06-20
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
assimp assimp to 6.0.4 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-404 The product does not release or incorrectly releases a resource before it is made available for re-use.
CWE-476 The product dereferences a pointer that it expects to be valid but is NULL.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a flaw found in the Assimp library up to version 6.0.4, specifically in the function Assimp::glTFImporter::ImportMeshes within the glTFImporter.cpp file. The flaw causes a null pointer dereference, which means the program attempts to access memory through a pointer that is null, leading to a crash or unexpected behavior.

The vulnerability can only be exploited locally, meaning an attacker must have local access to the system to trigger it. The issue has been publicly disclosed and an exploit is available.

Impact Analysis

The impact of this vulnerability is limited to causing a null pointer dereference, which can lead to a denial of service by crashing the application using the vulnerable Assimp component.

Since the attack requires local access and the vulnerability does not allow for code execution or data compromise, the overall impact is low.

Compliance Impact

The provided information does not specify any impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Detection Guidance

This vulnerability can be detected by triggering the null pointer dereference in the Assimp glTF importer's ImportMeshes function, typically by processing specially crafted glTF files that cause the crash.

Fuzzing the Assimp glTF importer with malformed or crafted glTF files is an effective detection method.

A proof-of-concept (PoC) exploit is available as a zip archive containing a glTF file that triggers the crash.

To detect the vulnerability on your system, you can run Assimp to import the provided PoC glTF file and observe if a crash or segmentation fault occurs.

  • Download the PoC zip archive from the provided resource.
  • Use a command like: assimp import ImportMeshes-segv.gltfux
  • Monitor for crashes or segmentation faults during import, which indicate the vulnerability is present.
Mitigation Strategies

Immediate mitigation steps include avoiding local execution of untrusted or malformed glTF files with the vulnerable Assimp versions up to 6.0.4.

Since the vulnerability requires local execution and causes a crash via null pointer dereference, restricting access to the Assimp library or applications using it can reduce risk.

Monitor for updates or patches from the Assimp project and apply them once available.

If possible, use input validation or sandboxing techniques to limit the impact of malformed glTF files.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-10198. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart