Application crash via unbounded FBX array allocation
Published May 4, 2026 · Updated May 4, 2026
Uncontrolled memory allocation in Assimp 6.0.2 allows attackers to crash an importing application with a crafted binary FBX file. ParseVectorDataArray() trusts the binary array count, passes it into buffer sizing, and reserves an output vector without an upper bound or consistency check. The target must import the attacker-supplied file through the FBX importer; excessive allocation then aborts or terminates that process.
Summary
What happened
Uncontrolled memory allocation in Assimp 6.0.2 allows attackers to crash an importing application with a crafted binary FBX file. ParseVectorDataArray() trusts the binary array count, passes it into buffer sizing, and reserves an output vector without an upper bound or consistency check. The target must import the attacker-supplied file through the FBX importer; excessive allocation then aborts or terminates that process.
The record
- CVE
- CVE-2025-70071
- Published
- May 4, 2026
- Updated
- May 4, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, CWE-770, CWE-1284, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 4, 2026CVE publishedPublication date reported by the CVE source.
- May 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo