Importer crash via unchecked glTF matrix length
Published May 31, 2026 · Updated May 31, 2026
Heap-buffer overflow in Assimp 6.0.0 through 6.0.4 allows local users to crash an importer with a malformed glTF2 file. In glTFCommon::CopyValue, the importer copies 16 floats from inverseBindMatrices data without first checking that the accessor supplies 64 bytes. A crafted local glTF2 file can make the 64-byte read overrun a one-byte heap allocation, causing an immediate process crash and an out-of-bounds memory read.
Summary
What happened
Heap-buffer overflow in Assimp 6.0.0 through 6.0.4 allows local users to crash an importer with a malformed glTF2 file. In glTFCommon::CopyValue, the importer copies 16 floats from inverseBindMatrices data without first checking that the accessor supplies 64 bytes. A crafted local glTF2 file can make the 64-byte read overrun a one-byte heap allocation, causing an immediate process crash and an out-of-bounds memory read.
The record
- CVE
- CVE-2026-10200
- Published
- May 31, 2026
- Updated
- May 31, 2026
- Vendor
- Open Asset Import Library
- Product
- Assimp
- Classifications
- CWE-119, CWE-122
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 31, 2026CVE publishedPublication date reported by the CVE source.
- May 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.0.0
- Affected versionversion=6.0.1
- Affected versionversion=6.0.2
- Affected versionversion=6.0.3
- Affected versionversion=6.0.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- CopyValue-heapof proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo