Quick answers
- Is CVE-2026-10198 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10198 being exploited in the wild.
- How severe is CVE-2026-10198?
- Low severity, with a CVSS score of 3.3, published 31 May 2026.
- Which products and versions are affected?
- Assimp up to 6.0.4.
- Is there a fix for CVE-2026-10198?
- 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-10198 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-10198?
- 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 null pointer dereference exists in the Assimp::glTFImporter::ImportMeshes function within glTFImporter.cpp. The vulnerability is caused by an unchecked return value from the ExtractData() function when processing texture coordinates. If ExtractData() fails due to an invalid bufferView or missing data, it returns a null pointer which is subsequently dereferenced. This issue can be triggered locally by providing a malformed glTF file, leading to a denial-of-service (crash). A proof-of-concept exploit has been publicly disclosed.
Affected products
- Assimp Assimp up to 6.0.4
Timeline
- 2026-04-24: disclosed: Issue reported on GitHub repository
- 2026-05-31: advisory: CVE published by VulDB/NVD