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

> Attackers can execute code or crash applications by supplying crafted glTF files with unchecked sparse indices to the cgltf library.

- **Severity:** High 7.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-6vjv-6x7m-3wjx

## What is CVE-2026-112018?

CVE-2026-112018 is a high-severity memory corruption vulnerability in jkuhlmann cgltf, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-112018?


## How do I fix CVE-2026-112018?

No fix has been published for CVE-2026-112018 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112018 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112018 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112018 and fix it if it is affected.

What it is: CVE-2026-112018 is a high-severity memory corruption vulnerability in jkuhlmann cgltf, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112018 exists.

Affected product: jkuhlmann cgltf. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112018/ (Markdown: https://insights.sbomify.com/CVE-2026-112018/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112018
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112018
- OSV: https://osv.dev/vulnerability/CVE-2026-112018

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112018/
Summaries are generated and may contain mistakes; the official description above is the record.