Local memory corruption via overflowing texture dimensions
Published Oct 5, 2025 · Updated Feb 24, 2026
Heap-based buffer overflow in Assimp 6.0.2 allows local users to corrupt memory by importing a crafted Q3D model file. The Q3D importer multiplies untrusted texture dimensions in an unsigned integer, allocates the wrapped size, then writes texture bytes past the heap buffer. Reachability requires local processing of a malicious Q3D file; the demonstrated result is an application crash with memory corruption.
Summary
What happened
Heap-based buffer overflow in Assimp 6.0.2 allows local users to corrupt memory by importing a crafted Q3D model file. The Q3D importer multiplies untrusted texture dimensions in an unsigned integer, allocates the wrapped size, then writes texture bytes past the heap buffer. Reachability requires local processing of a malicious Q3D file; the demonstrated result is an application crash with memory corruption.
The record
- CVE
- CVE-2025-11277
- Published
- Oct 5, 2025
- Updated
- Feb 24, 2026
- Vendor
- Open Asset Import Library
- Product
- Assimp
- Classifications
- CWE-119, CWE-122, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 5, 2025CVE publishedPublication date reported by the CVE source.
- Feb 24, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.0.2
What conditions does exploitation require?
What is affected?
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
- Q3DImporter crafted-file proof of conceptproof of concept · demonstrated
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