cve.bz

CVE-2026-134861 Assimp through 6.0.6 Out-of-Bounds Write via glTF 1.0 Accessor Element Size

6.9 mediumFix available

Medium (6.9) in assimp assimp.

Assimp through 6.0.6 contains an out-of-bounds write vulnerability in glTFAsset.inl that allows attackers to corrupt memory via oversized glTF 1.0 accessor elements. Attackers can supply a crafted glTF 1.0 file with VEC4 position or VEC3 index accessors to overflow heap or stack buffers during import, crashing applications.

Severity

CVSS 4.0

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

CVSS 3.1

6.1 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
CWE
CWE-787 Out-of-bounds Write
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-134861 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-134861?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-134861?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-134861 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
assimpthrough 6.0.6

References

Check your stackJSON