Quick answers
- Is CVE-2026-19969 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19969 being exploited in the wild.
- How severe is CVE-2026-19969?
- Medium severity, with a CVSS score of 5.4, published 17 August 2026.
- Which products and versions are affected?
- Assimp 17c12da.
- Is there a fix for CVE-2026-19969?
- 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-19969 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-19969?
- 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 buffer overflow exists in the Assimp::MDLImporter::GenerateOutputMeshes_3DGS_MDL7 function in code/AssetLib/MDL/MDLLoader.cpp at line 1944. The vulnerability is triggered during 3DGS MDL7 model file parsing when a loop index (iCurrent) exceeds the bounds of an allocated array (pcMesh->mBones), causing out-of-bounds writes. The attack vector is network-based: a remote attacker can craft a malicious .mdl file and supply it to an application that uses Assimp for model loading, without requiring authentication or user interaction. The PoC has been disclosed publicly. No patch has been released at the time of advisory publication.
Affected products
- Assimp Assimp 17c12da
Timeline
- 2026-08-17: disclosed