CVE-2026-10200: Assimp 6.0.4 Heap Buffer Overflow in glTF Matrix Parser

Technical summary

CVE-2026-10200 exists in the glTFCommon::CopyValue function within glTFCommon.h, which handles parsing of 4x4 matrices in glTF model files. The vulnerability is classified as a heap-based buffer overflow (CWE-119, CWE-122) resulting from improper bounds checking during matrix value copying operations. The flaw allows a local attacker to write beyond allocated heap memory by providing a specially crafted glTF file, potentially corrupting heap structures and enabling further exploitation.

Business impact

This vulnerability primarily affects organizations and individuals using Assimp for 3D model processing in applications such as game engines, CAD software, 3D visualization tools, and asset pipelines. While exploitation requires local access, the public nature of the exploit means any organization relying on Assimp 6.0.4 or earlier faces real risk. Potential impacts include denial of service through application crashes, data exfiltration from the process memory space, or, in more sophisticated scenarios, privilege escalation or arbitrary code execution depending on the application's context and privileges.

Affected systems

Assimp versions up to and including 6.0.4 are affected. The vulnerability resides in the glTF parsing component, so any application embedding or depending on vulnerable Assimp versions that processes untrusted or user-supplied glTF files is at risk. This includes game development frameworks, 3D modeling software, web services that accept 3D model uploads, and any tool in a content creation pipeline that uses Assimp for model import.

Exploitability

The vulnerability has a CVSS v3.1 score of 5.3 (MEDIUM) with the vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, indicating that exploitation requires local access (AV:L) and a user account with low privileges (PR:L). No user interaction is needed (UI:N). While not remotely exploitable without additional attack vectors, the public availability of exploit code significantly lowers the barrier to weaponization for any attacker with local system access or the ability to place files on an affected system.

Remediation

Immediately upgrade Assimp to a patched version after 6.0.4; verify the latest stable release on the Assimp GitHub repository. For applications embedding Assimp, coordinate with your build and dependency management systems to pull the updated library version. If immediate patching is not feasible, implement input validation to reject suspicious glTF files and restrict file processing to trusted sources only. Reduce local access surface area by enforcing principle of least privilege and monitoring for suspicious file uploads or local file placement.

Patch guidance

Update Assimp to a version newer than 6.0.4. Verify the exact patched version in the official Assimp repository releases or security advisories. For applications with Assimp as a dependency, check your package manager (pip, npm, vcpkg, etc.) for the latest available version and perform regression testing after update. If your application vendors Assimp, rebuild and redeploy with the patched library version.

Detection guidance

Monitor for crafted glTF files with unusual or oversized 4x4 matrix data entering your processing pipelines. Look for application crashes or unexpected memory behavior when processing glTF files from untrusted sources. Implement file integrity monitoring and logging around glTF file ingestion. On systems where Assimp runs, monitor for heap corruption signatures and unusual process terminations related to 3D model processing tools.

Why prioritize this

Although the CVSS score of 5.3 is moderate, prioritize patching because: (1) the vulnerability has public exploit code available, significantly reducing exploitation difficulty; (2) Assimp is widely used in asset pipelines and creative workflows where untrusted files may be processed; (3) even though local access is required, insider threats and compromised user accounts are common attack vectors; (4) any remote file upload feature serving glTF models could expose your infrastructure if combined with other vulnerabilities.

Risk score, explained

The CVSS score of 5.3 reflects a local-only attack vector and low-privilege requirement, which constrains the immediate threat. However, the publication of exploit code elevates practical risk significantly. The LOW impact on confidentiality, integrity, and availability (each marked 'L') suggests bounded but real harm per successful exploit. Organizations should weight the moderate score against their specific exposure: if you process untrusted glTF files or operate multi-user systems, effective risk is higher than the CVSS number alone suggests.

Frequently asked questions