Quick answers
- Is CVE-2026-111128 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111128 being exploited in the wild.
- How severe is CVE-2026-111128?
- Medium severity, with a CVSS score of 5.5, published 15 October 2026.
- Which products and versions are affected?
- Assimp through 6.0.5.
- Is there a fix for CVE-2026-111128?
- 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-111128 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-111128?
- 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
The vulnerability is a NULL pointer dereference in OgreStructs.cpp where the Ogre3D importer fails to validate bone indices before use. When processing a crafted .mesh or .skeleton file that references a non-existent bone, the BoneById() function returns null but is dereferenced without checking, causing a crash. This requires the attacker to control the input file supplied to the application.
Affected products
- Assimp Assimp through 6.0.5
Timeline
- 2026-10-15: disclosed