# CVE-2026-10200: Assimp 4x4 Matrix glTFCommon.h CopyValue heap-based overflow

> A heap-based buffer overflow in Assimp's glTF parser allows local attackers to execute arbitrary code or cause denial of service via crafted files.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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-10200, GHSA-x9p9-4cp2-p368, UBUNTU-CVE-2026-10200

## What is CVE-2026-10200?

CVE-2026-10200 is a medium-severity memory corruption 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 found in Assimp up to 6.0.4. This affects the function glTFCommon::CopyValue in the library glTFCommon.h of the component 4x4 Matrix Parser. Performing a manipulation results in heap-based buffer overflow. The attack must be initiated from a local position. The exploit has been made public and could be used. The project tagged the reported issue as bug.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

Upgrade to a fixed version.

## Is CVE-2026-10200 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10200 is a medium-severity memory corruption 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-10200 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-10200/ (Markdown: https://insights.sbomify.com/CVE-2026-10200/index.md)
```

## Sources

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

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