CVE-2026-112019 jkuhlmann CVE debrief

Who should care

Defenders responsible for systems or applications that utilize the cgltf library should assess exposure and prioritize verification and remediation efforts. This includes developers, security teams, and IT professionals managing applications that process glTF or GLB files.

Why it matters

CVE-2026-112019 is a medium-severity vulnerability in the cgltf library that could allow attackers to read adjacent heap memory or crash applications by supplying crafted glTF or GLB files. Defenders should prioritize verifying the affected version of cgltf, applying patches, and implementing input validation to prevent exploitation.

• Potential for data breaches through unauthorized access to sensitive data in adjacent heap memory.
• Risk of application crashes or denial-of-service conditions.
• Need for verification of affected versions and application of patches or mitigations.
• Potential for attackers to supply crafted files that could lead to information disclosure.

Technical summary

The cgltf library through version 1.15 contains a heap out-of-bounds read vulnerability in the cgltf_accessor_unpack_floats() function. This function improperly advances the sparse values cursor by the base bufferView byteStride, allowing attackers to supply crafted glTF or GLB files that pass validation to read adjacent heap memory or cause application crashes. The vulnerability is a result of the library's failure to properly validate the input files, which can lead to potential security issues. Defenders should prioritize verifying the affected version of cgltf and applying patches or mitigations as available.

Defensive priority

Defenders should prioritize verifying the affected version of cgltf and applying patches or mitigations as available.

Recommended defensive actions

• Verify the version of cgltf in use and apply patches or updates as available.
• Implement input validation and sanitization to prevent the supply of crafted glTF or GLB files.
• Monitor applications for crashes or unexpected behavior that may indicate exploitation attempts.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and potential impact. However, the corpus does not establish versions, exploitation, impact, or remediation beyond what is provided by the official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.