Memory-Disclosure — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/memory-disclosure/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 23 Mar 2026 16:16:48 +0000cgltf Integer Overflow Vulnerability in Sparse Accessor Validationhttps://feed.craftedsignal.io/briefs/2026-03-cgltf-overflow/Mon, 23 Mar 2026 16:16:48 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-03-cgltf-overflow/cgltf version 1.15 and prior contain an integer overflow vulnerability in the cgltf_validate() function when validating sparse accessors, allowing attackers to trigger out-of-bounds reads via crafted glTF/GLB files, leading to denial of service and potential memory disclosure.cgltf is a minimalist C library for loading glTF 2.0 files. Versions 1.15 and earlier are vulnerable to an integer overflow in the cgltf_validate() function. This vulnerability occurs during the validation of sparse accessors within glTF/GLB files. An attacker can exploit this by crafting malicious glTF/GLB files with specifically chosen size values that trigger integer overflows in arithmetic operations during sparse accessor validation. Successful exploitation leads to out-of-bounds reads due to heap buffer over-reads in cgltf_calc_index_bound(). This results in a denial-of-service condition (application crash) and potentially leads to memory disclosure. Defenders should monitor applications parsing glTF/GLB files for unexpected crashes or abnormal memory access patterns.

Attack Chain

  1. The attacker crafts a malicious glTF or GLB file.
  2. The crafted file contains a sparse accessor with attacker-controlled size values designed to cause an integer overflow.
  3. The vulnerable application uses the cgltf library to parse the malicious glTF/GLB file.
  4. The cgltf_validate() function is called to validate the glTF data, including the sparse accessor.
  5. During sparse accessor validation, unchecked arithmetic operations occur with the attacker-controlled size values, resulting in an integer overflow.
  6. The integer overflow leads to an incorrect calculation of the index bound in the cgltf_calc_index_bound() function.
  7. cgltf_calc_index_bound() attempts to access a heap buffer using the incorrect index bound.
  8. This results in an out-of-bounds read, causing a denial of service (application crash) or potentially exposing sensitive memory contents.

Impact

Successful exploitation of this vulnerability results in a denial-of-service condition, as the application parsing the malicious glTF/GLB file crashes. Furthermore, the out-of-bounds read could potentially expose sensitive information from the application’s memory. The number of potential victims depends on the prevalence of applications using the vulnerable cgltf library to process potentially untrusted glTF/GLB files. Sectors affected could include any application that handles 3D models or scenes using the glTF format, such as game development, CAD software, and visualization tools.

Recommendation

  • Upgrade to a patched version of the cgltf library that addresses CVE-2026-32845.
  • Implement input validation on glTF/GLB files before parsing them with cgltf to prevent malicious size values from reaching the vulnerable cgltf_validate() function.
  • Deploy the Sigma rule “Detect glTF Parsing Process Crash” to identify processes crashing while parsing glTF/GLB files, which can indicate exploitation attempts.
  • Enable process crash reporting to collect detailed information about crashes, including memory dumps, which can aid in identifying the root cause and potential memory disclosure.
]]>highadvisoryinteger-overflowdenial-of-servicememory-disclosureglTFcgltf