Code execution via malformed MODEL file parsing
Published Dec 15, 2025 · Updated Dec 15, 2025
Out-of-bounds write in Autodesk Shared Components before 2026.5 allows attackers to execute code through a crafted MODEL file. The MODEL file parser writes beyond an allocated buffer while processing malformed file data; Autodesk has not disclosed the responsible executable or function. Opening the file in an affected Autodesk host application is required, and successful exploitation runs code in the current process or causes a crash or data corruption.
Summary
What happened
Out-of-bounds write in Autodesk Shared Components before 2026.5 allows attackers to execute code through a crafted MODEL file. The MODEL file parser writes beyond an allocated buffer while processing malformed file data; Autodesk has not disclosed the responsible executable or function. Opening the file in an affected Autodesk host application is required, and successful exploitation runs code in the current process or causes a crash or data corruption.
The record
- CVE
- CVE-2025-10900
- Published
- Dec 15, 2025
- Updated
- Dec 15, 2025
- Vendor
- Autodesk
- Product
- Autodesk Shared Components
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2025CVE publishedPublication date reported by the CVE source.
- Dec 15, 2025Record 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.0 <2026.5
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