CVE Intelligence
High Memory corruption

CVE-2026-112018 — cgltf through 1.15 Heap Out-of-Bounds Write via cgltf_accessor_unpack_floats()

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.

Published Oct 18, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (high)+6
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.13%
ahead of 2% of scored CVEs · Oct 20, 2026
Affects
Jkuhlmann
Cgltf
CVSS base
7.0
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Jkuhlmann Cgltf).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Jkuhlmann Cgltf ≤ 1.15 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.3 CVSS 4.0 High — — disclosure@vulncheck.com via NIST National Vulnerability Database
7.3 CVSS 4.0 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
7.0 CVSS 3.1 High 1.0 5.9 disclosure@vulncheck.com via NIST National Vulnerability Database
7.0 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.0 CVSS 3.1 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

EPSS over time FIRST

Oct 19, 2026 → Oct 20, 2026 · 2 reading(s) · max 0.13%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · jkuhlmann/cgltf
    Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 18, 2026
  • CVSS changed · 7.0
    Oct 18, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 18, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 18, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 18, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 18, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 18, 2026 – Oct 18, 2026

References

7 on the record

Elsewhere on this site

Jkuhlmann
every CVE for this vendor
Memory corruption
same class
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-112019 cgltf through 1.15 Heap Out-of-Bounds Read via cgltf_accessor_unpack_floats() 3d
  • CVE-2026-75148 cgltf 1.15 Integer Overflow via cgltf_validate() Accessor Bounds Check Aug 19, 2026
  • CVE-2026-32845 jkuhlmann / cgltf <= 1.15 Sparse Accessor Validation Integer Overflow Mar 23, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-112018 is "cgltf through 1.15 Heap Out-of-Bounds Write via cgltf_accessor_unpack_floats()", rated High. It affects Cgltf (Jkuhlmann); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.0 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.