Live › vulnerability › CVE-2026-117608
Go to dashboardAssimp through 6.0.5 has an integer overflow in its MD2 importer header validation. A crafted .md2 model file can bypass frame table bounds checks, causing out-of-bounds heap reads that crash the application or expose adjacent heap memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 03:31 UTC. All times on this page are UTC.
Applications that use Assimp to load untrusted .md2 model files, such as user uploads or third-party assets, are exposed. Applications that only load models you ship yourself, or that never import MD2 files, have a much smaller exposure and can skip it until a fixed version is available.
No product ranges from the sources yet.
pkg-config --modversion assimp or the version in your package manifest; anything through 6.0.5 is in scope.grep -ri assimp in build files and lockfiles, to find where it is bundled.Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Assimp through 6.0.5 contains an integer overflow vulnerability in MD2Importer::ValidateHeader() that allows attackers to bypass frame table bounds checks using crafted header fields. Attackers can supply a malicious .md2 file whose numFrames and numVertices values wrap the 32-bit size check, causing heap out-of-bounds reads that crash applications or expose adjacent heap memory.
This page as .md · .json · in your agent: get_signal("CVE-2026-117608")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.