Quick answers
- Is CVE-2026-19970 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19970 being exploited in the wild.
- How severe is CVE-2026-19970?
- Medium severity, with a CVSS score of 6.3, published 17 August 2026.
- Which products and versions are affected?
- Assimp commit 17c12da and likely other versions.
- Is there a fix for CVE-2026-19970?
- 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-19970 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-19970?
- 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 heap-based buffer overflow in the MDLImporter::AddBonesToNodeGraph_3DGS_MDL7 function within MDLLoader.cpp. The flaw is triggered by improper validation of the bones_num argument when parsing MDL (Quake engine) model files, allowing an attacker to write beyond allocated memory bounds. The attack requires an attacker to craft and serve a malicious MDL file; exploitation occurs when a victim application loads the file using Assimp. The attack is remotely exploitable with no authentication required, though it does require a user or application to explicitly load a crafted model file. A public proof-of-concept exploit is available. At time of disclosure, the Assimp project had not released a patch.
Affected products
- Assimp Assimp commit 17c12da and likely other versions
Timeline
- 2026-08-17: disclosed: CVE-2026-19970 published on NVD
- 2026-08-17: advisory: Public proof-of-concept exploit released