Quick answers
- Is CVE-2026-10231 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10231 being exploited in the wild.
- How severe is CVE-2026-10231?
- Medium severity, with a CVSS score of 5.3, published 1 June 2026.
- Which products and versions are affected?
- Assimp up to 6.0.4.
- Is there a fix for CVE-2026-10231?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-10231 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-10231?
- Check whether you run Assimp 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 Assimp versions up to 6.0.4 within the HL1MDLLoader::extract_anim_value function in HL1MDLLoader.cpp. The vulnerability is triggered by manipulating the 'num.total' argument, specifically when it is set to zero, leading to improper memory bounds handling during the extraction of animation values from Half-Life 1 MDL files. An attacker with local access can exploit this by providing a malformed MDL file to an application using the library. Successful exploitation could result in a denial-of-service (crash) or potentially limited information disclosure and integrity loss. A public proof-of-concept exploit has been released.
Affected products
- Assimp Assimp up to 6.0.4
Timeline
- 2026-06-01: advisory: Vulnerability published by VulDB and NVD