CVE-2026-129479
Received Received - Intake

Integer Overflow in Assimp via Ogre Binary .mesh Files

Publication date: 2026-11-15

Last updated on: 2026-11-15

Assigner: VulnCheck

Description
Assimp through 6.0.6 contains an integer overflow vulnerability in OgreBinarySerializer::ReadSubMesh that allows attackers to crash applications by supplying crafted Ogre binary .mesh files. Attackers can set a large index count so the 32-bit buffer size wraps, causing a segmentation fault in aiMesh::~aiMesh() during scene teardown.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-15
Last Modified
2026-11-15
Generated
2026-11-15
AI Q&A
2026-11-15
EPSS Evaluated
N/A
NVD
CVE-2026-129479
EUVD
EUVD-2026-126028

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
assimp assimp From 0 (inc) to 6.0.6 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-190 The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-129479 is an integer overflow vulnerability in the Assimp library (versions up to 6.0.6) affecting the OgreBinarySerializer::ReadSubMesh function. Attackers exploit this by crafting malicious Ogre binary .mesh files with a large index count. The 32-bit buffer size calculation wraps around, causing a segmentation fault during scene teardown in aiMesh::~aiMesh().

The root cause is a memory-safety issue (CWE-190) where undersized allocation occurs due to file-controlled fields, leading to inconsistent scene data and crashes.

Detection Guidance

To detect this vulnerability, monitor for crashes in applications using Assimp when processing Ogre binary .mesh files. Use AddressSanitizer or Valgrind to detect memory corruption during file parsing. Check for segmentation faults in aiMesh::~aiMesh() or aiScene::~aiScene() during application teardown.

Impact Analysis

This vulnerability allows attackers to crash applications processing Ogre mesh files, causing denial of service. It does not enable code execution or data theft but disrupts normal operations by triggering segmentation faults during cleanup.

The impact is limited to applications using Assimp to import Ogre mesh files, particularly those with default configurations. No special preconditions are required for exploitation.

Compliance Impact

This vulnerability primarily causes denial-of-service conditions by crashing applications via crafted files. It does not directly impact data confidentiality or integrity, which are key concerns for GDPR and HIPAA. However, repeated crashes could disrupt services handling sensitive data, potentially leading to compliance issues if availability is compromised.

Mitigation Strategies

Update Assimp to the latest patched version that fixes the integer overflow in OgreBinarySerializer::ReadSubMesh. Avoid processing untrusted Ogre .mesh files until patched. Implement file validation to reject malformed files before parsing.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-129479. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...