CVE-2026-112018
Deferred Deferred - Pending Action

Heap Out-of-Bounds Write in cgltf Library

Vulnerability report for CVE-2026-112018, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-18

Last updated on: 2026-10-18

Assigner: VulnCheck

Description

cgltf through 1.15 contains a heap out-of-bounds write vulnerability in cgltf_accessor_unpack_floats() that allows attackers to write outside the output buffer via unchecked sparse accessor indices. Attackers can supply a crafted glTF or GLB file with large sparse indices to corrupt heap memory, crash applications, and potentially execute code when cgltf_validate() is not called.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-18
Last Modified
2026-10-18
Generated
2026-10-18
AI Q&A
2026-10-18
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
jkuhlmann cgltf 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a heap out-of-bounds write vulnerability in the cgltf library version 1.15 and earlier. It occurs in the function cgltf_accessor_unpack_floats() when processing sparse accessor indices in glTF or GLB files. Attackers can craft malicious files with large sparse indices to write data outside the intended output buffer, corrupting heap memory, causing crashes, or potentially executing arbitrary code if input validation is skipped.

Detection Guidance

To detect this vulnerability, inspect glTF/GLB files processed by cgltf for large sparse indices or malformed buffer views. Use tools like file inspection utilities to check file integrity. Monitor applications using cgltf for crashes or memory corruption when parsing 3D assets. Validate files with cgltf_validate() if available.

Impact Analysis

If you use applications that rely on cgltf to parse glTF or GLB files, this vulnerability could allow attackers to crash your software, corrupt memory, or execute malicious code by tricking you into opening a specially crafted 3D model file. The impact depends on whether the application calls cgltf_validate() to check input files.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling arbitrary code execution or data corruption through crafted glTF files. If exploited, it may lead to unauthorized access, data breaches, or integrity violations, which are critical concerns under these regulations. The lack of validation in cgltf_validate() exacerbates this risk.

Mitigation Strategies

Immediately update cgltf to the latest patched version. If updating is not possible, ensure cgltf_validate() is called before processing files. Avoid parsing untrusted glTF/GLB files. Implement input validation for sparse indices and buffer views. Monitor for crashes or memory corruption in applications handling 3D assets.

Chat Assistant

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

EPSS Chart