# CVE-2026-10198: Assimp glTFImporter glTFImporter.cpp ImportMeshes null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in the Assimp library's glTF importer.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-10198, GHSA-7m2c-m24q-64cc, UBUNTU-CVE-2026-10198

## What is CVE-2026-10198?

CVE-2026-10198 is a medium-severity vulnerability in Assimp, published on 31 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in Assimp up to 6.0.4. Affected by this vulnerability is the function Assimp::glTFImporter::ImportMeshes of the file glTFImporter.cpp of the component glTFImporter. This manipulation causes null pointer dereference. The attack is restricted to local execution. The exploit has been published and may be used. The project tagged the reported issue as bug.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-10198 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10198 is a medium-severity vulnerability in Assimp, published on 31 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10198 exists.

Affected product: Assimp. 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-10198/ (Markdown: https://insights.sbomify.com/CVE-2026-10198/index.md)
```

## Sources

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

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