Quick answers
- Is CVE-2026-82591 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82591 being exploited in the wild.
- How severe is CVE-2026-82591?
- Medium severity, with a CVSS score of 5.3, published 30 August 2026.
- Which products and versions are affected?
- Assimp Open Asset Import Library up to 6.0.2.
- Is there a fix for CVE-2026-82591?
- A patch was published on 2026-08-04: Fix merged in upstream repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82591 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-82591?
- Check whether you run Assimp Open Asset Import Library at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap-based buffer overflow exists in the MD5Importer::MakeDataUnique function in code/AssetLib/MD5/MD5Loader.cpp, triggered by improper handling of the iNewIndex argument during memory manipulation. The vulnerability requires local access and a specially crafted MD5 model file to trigger. An attacker can cause a heap buffer overflow write, leading to application crash (denial of service) or potential code execution depending on heap layout. A patch has been identified (commit bf9dabb617c46e5133dac65cca6bff177917afcb) and is available in the upstream repository.
Affected products
- Assimp Open Asset Import Library up to 6.0.2
Timeline
- 2026-08-30: disclosed
- 2026-08-04: patched: Fix merged in upstream repository