# CVE-2026-82591: Open Asset Import Library Assimp MD5Loader.cpp MakeDataUnique heap-based overflow

> A heap-based buffer overflow in Assimp's MD5 loader 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:X`)
- **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:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-82591, GHSA-4pff-rvgp-gggv, OESA-2026-4021, OESA-2026-4022, OESA-2026-4023, OESA-2026-4024, UBUNTU-CVE-2026-82591

## What is CVE-2026-82591?

CVE-2026-82591 is a medium-severity memory corruption vulnerability in Open Asset Import Library Assimp, published on 30 Aug 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 Open Asset Import Library Assimp up to 6.0.2. The impacted element is the function MD5Importer::MakeDataUnique of the file code/AssetLib/MD5/MD5Loader.cpp. The manipulation of the argument iNewIndex leads to heap-based buffer overflow. The attack can only be performed from a local environment. The identifier of the patch is bf9dabb617c46e5133dac65cca6bff177917afcb. Applying a patch is the recommended action to fix this issue.

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-82591?


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

Apply the vendor's patch.

## Is CVE-2026-82591 being exploited?

There is no known exploitation of CVE-2026-82591 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82591 is a medium-severity memory corruption vulnerability in Open Asset Import Library Assimp, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82591 in the wild and no public exploit code.

Affected product: Open Asset Import Library 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-82591/ (Markdown: https://insights.sbomify.com/CVE-2026-82591/index.md)
```

## Sources

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

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