Quick answers
- Is CVE-2026-10232 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10232 being exploited in the wild.
- How severe is CVE-2026-10232?
- 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-10232?
- 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-10232 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-10232?
- 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-use-after-free vulnerability exists in Assimp up to version 6.0.4 within the ASE (ASCII Scene Export) file parser. The flaw is located in the aiNode::~aiNode() destructor in scene.cpp, which is triggered during recursive node destruction when processing a malformed ASE file. An attacker can exploit this by providing a crafted ASE file that creates an invalid node tree, leading to a use-after-free condition during memory deallocation. This requires local access to provide the malicious file to the library. A public proof-of-concept (PoC) has been released.
Affected products
- Assimp Assimp up to 6.0.4
Timeline
- 2026-06-01: disclosed: Vulnerability disclosed and CVE assigned
- 2026-06-01: advisory