# CVE-2026-10197: Assimp TF File glTF2Importer.cpp ImportEmbeddedTextures null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in Assimp's glTF2 importer when processing embedded textures.

- **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-10197, GHSA-2r76-r3fx-jwv2, UBUNTU-CVE-2026-10197

## What is CVE-2026-10197?

CVE-2026-10197 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 was detected in Assimp up to 6.0.4. Affected is the function glTF2Importer::ImportEmbeddedTextures in the library code/AssetLib/glTF2/glTF2Importer.cpp of the component TF File Handler. The manipulation results in null pointer dereference. The attack is only possible with local access. The exploit is now public and may be used. It is advisable to implement a patch to correct this issue. The pull request to fix this issue awaits acceptance.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-10197 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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