# CVE-2026-10199: Assimp glTF2Asset.h LazyDict null pointer dereference

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

- **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:** Yes
- **Published:** 31 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-10199, GHSA-6rfw-vrjc-wff7, UBUNTU-CVE-2026-10199

## What is CVE-2026-10199?

CVE-2026-10199 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 vulnerability has been found in Assimp up to 6.0.4. Affected by this issue is the function glTF2::LazyDict in the library glTF2Asset.h. Such manipulation of the argument operator[] leads to null pointer dereference. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. The name of the patch is d24b85319bd70c65883a2b96613e07e23fb95981. It is best practice to apply a patch to resolve this issue.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-10199 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10199 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-10199 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-10199/ (Markdown: https://insights.sbomify.com/CVE-2026-10199/index.md)
```

## Sources

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

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