cve.bz

CVE-2026-134866 Assimp 6.0.0 through 6.0.6 Infinite Loop via Comment Line in SkipLine

6.8 mediumFix available

Medium (6.8) in assimp assimp.

Assimp 6.0.0 through 6.0.6 contains an infinite loop vulnerability in SkipLine that allows attackers to hang parsing by supplying files with '#' comment lines. Attackers can provide crafted OFF, LWS, or MD3 shader files so ReadFile never returns, consuming a CPU core and denying service.

Severity

CVSS 4.0

6.8 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CWE
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Assigned by
VulnCheck (CNA)
NVD analysis
Not in the NVD yet
Record from
the CVE List, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-134866 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-134866?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-134866?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-134866 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
assimpfrom 6.0.0 through 6.0.6

References

Check your stackJSON