# CVE-2026-10233: Assimp Half-Life 1 MDL Loader HL1MDLLoader.cpp read_sequence_infos out-of-bounds

> A local attacker can trigger an out-of-bounds read in the Assimp library's Half-Life 1 MDL loader, potentially causing crashes or leaking memory.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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:** 1 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-10233, GHSA-964j-jgrw-m572, UBUNTU-CVE-2026-10233

## What is CVE-2026-10233?

CVE-2026-10233 is a medium-severity memory corruption vulnerability in Assimp, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability has been detected in Assimp up to 6.0.4. Affected by this issue is the function HL1MDLLoader::read_sequence_infos of the file HL1MDLLoader.cpp of the component Half-Life 1 MDL Loader. The manipulation of the argument aiString leads to out-of-bounds read. The attack needs to be performed locally. The exploit has been disclosed publicly and may be used. The project tagged the reported issue as bug.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-10233 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10233 is a medium-severity memory corruption vulnerability in Assimp, published on 1 Jun 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-10233 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-10233/ (Markdown: https://insights.sbomify.com/CVE-2026-10233/index.md)
```

## Sources

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

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