Security readout for executives and security teams
Plain-English summary
CVE-2026-32845 affects cgltf 1.15 and earlier when parsing crafted glTF/GLB files. A malicious 3D asset can trigger unsafe memory reads, causing application crashes and possible memory exposure. Treat this as high priority where cgltf handles untrusted or customer-supplied assets.
Executive priority
Prioritize remediation for any internet-facing or customer-facing 3D asset workflow. Lower urgency may be reasonable for isolated internal-only tooling that never processes untrusted files.
Technical view
cgltf_validate() has unchecked integer arithmetic during sparse accessor validation. Crafted sparse accessor size values can overflow calculations and lead to heap buffer over-reads in cgltf_calc_index_bound(). The reported impact is denial of service and potential memory disclosure.
Likely exposure
Exposure is most likely in software, services, import pipelines, or desktop tools that embed cgltf 1.15 or earlier and parse untrusted glTF/GLB content.
Exploitation context
The source bundle references technical details and exploit-related material, but does not show active exploitation. KEV status is false. Exploitation requires a crafted glTF/GLB file being processed by vulnerable cgltf code.
Researcher notes
Evidence supports integer overflow leading to heap over-read, crash, and possible disclosure. The bundle does not establish remote exploitation, active exploitation, or a finalized fixed version. Avoid assuming code execution from the provided facts.
Mitigation direction
- Inventory products and services that embed cgltf.
- Check upstream cgltf guidance, issue 287, and pull request 293 for fix status.
- Update cgltf when a fixed upstream version or commit is confirmed.
- Restrict or sandbox processing of untrusted glTF/GLB files.
- Apply file validation and size limits before cgltf parsing.
Validation and detection
- Search dependency manifests and vendored source for cgltf usage.
- Confirm whether deployed code uses cgltf 1.15 or earlier.
- Review asset ingestion paths that accept glTF or GLB files.
- Check crash telemetry for cgltf validation or bounds calculation failures.
- Track the CVE record and VulnCheck advisory for updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-32845 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9VulnCheckCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jkuhlmann/cgltf/issues/287CVE reference, VulnCheck · technical-description, exploit
- https://github.com/jkuhlmann/cgltf/pull/293CVE reference, VulnCheck · issue-tracking
- https://www.vulncheck.com/advisories/jkuhlmann-cgltf-sparse-accessor-validation-integer-overflowCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.