CVE-2026-10200
Heap-based Buffer Overflow in Assimp 4x4 Matrix Parser
Publication date: 2026-05-31
Last updated on: 2026-05-31
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| assimp | assimp | to 6.0.4 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Assimp library up to version 6.0.4, specifically in the function glTFCommon::CopyValue within the glTFCommon.h component that handles 4x4 Matrix Parsing.
The issue is a heap-based buffer overflow caused by improper handling or manipulation of data in this function.
An attacker must have local access to initiate the exploit, and the exploit code has been made publicly available.
The project has classified this issue as a bug.
How can this vulnerability impact me? :
This vulnerability can lead to a heap-based buffer overflow, which may allow an attacker with local access to corrupt memory.
Such memory corruption could potentially be exploited to cause a crash, execute arbitrary code, or escalate privileges depending on the environment and usage.
However, the CVSS scores indicate a relatively low to moderate severity, with the highest being 5.3 (medium severity) in version 3.1.