Code execution via MODEL parser buffer overwrite
Published Feb 18, 2026 · Updated Feb 18, 2026
Out-of-bounds write in Autodesk Shared Components 2026.5 and earlier allows attackers to execute code through a crafted MODEL file. The MODEL parser fails to validate user-supplied data before writing it, allowing a write past the end of an allocated buffer. Exploitation requires a user to open a malicious file or visit attacker-controlled content and runs code in the current process, with crash and data corruption also possible.
Summary
What happened
Out-of-bounds write in Autodesk Shared Components 2026.5 and earlier allows attackers to execute code through a crafted MODEL file. The MODEL parser fails to validate user-supplied data before writing it, allowing a write past the end of an allocated buffer. Exploitation requires a user to open a malicious file or visit attacker-controlled content and runs code in the current process, with crash and data corruption also possible.
The record
- CVE
- CVE-2026-0875
- Published
- Feb 18, 2026
- Updated
- Feb 18, 2026
- Vendor
- Autodesk
- Product
- Autodesk Shared Components
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2026CVE publishedPublication date reported by the CVE source.
- Feb 18, 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=2026.5 <2026.6
What conditions does exploitation require?
What is affected?
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