Skip to main content

CVE-2026-112018: Out-of-bounds Write in jkuhlmann cgltf

0
High
Published: 10/18/2026 (10/18/2026, 12:30:28 UTC)
Source: CVE Database V5
Vendor/Project: jkuhlmann
Product: cgltf

Description

cgltf versions up to 1.15 contain a heap out-of-bounds write vulnerability in the function cgltf_accessor_unpack_floats(). This flaw allows attackers to write outside the intended output buffer by supplying crafted glTF or GLB files with large sparse indices. Exploitation can lead to heap memory corruption, application crashes, and potentially code execution if cgltf_validate() is not used.

CVSS v4.0

Score 7.3high

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
Passive
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
High
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Affected software

jkuhlmann

cgltf

Affected versions
>=0 <=1.15
GitHub Actionsmore threats →cve
cgltf
pkg:github/cgltf
Affected versions
>=0 <=1.15

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/18/2026, 12:03:17 UTC

Technical Analysis

CVE-2026-112018 is a heap out-of-bounds write vulnerability in the cgltf library (up to version 1.15) within the cgltf_accessor_unpack_floats() function. The vulnerability arises from unchecked sparse accessor indices, enabling an attacker to write beyond the allocated output buffer. By providing a specially crafted glTF or GLB file containing large sparse indices, an attacker can corrupt heap memory, cause application crashes, and possibly achieve code execution if the function cgltf_validate() is not invoked to validate input.

Potential Impact

Successful exploitation can result in heap memory corruption, leading to application instability or crashes. There is also potential for arbitrary code execution if input validation via cgltf_validate() is omitted. This poses a high risk to applications using vulnerable versions of cgltf that process untrusted glTF or GLB files.

Mitigation Recommendations

Users should ensure that cgltf_validate() is called to validate input files before processing. Additionally, upgrading to a patched version beyond 1.15 is recommended once available. Patch status is not yet confirmed—check the vendor advisory for current remediation guidance.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-10-18T01:24:50.766Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ad4b23c2cdf04f65664e4c2

Added to database: 10/18/2026, 11:49:16 UTC

Last enriched: 10/18/2026, 12:03:17 UTC

Last updated: 10/18/2026, 19:55:33 UTC

Views: 12

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses