CVE-2025-10900 Overview
CVE-2025-10900 is an out-of-bounds write vulnerability [CWE-787] affecting Autodesk Shared Components and a broad set of Autodesk 2026 products. A maliciously crafted MODEL file, when parsed by an affected application, triggers memory corruption outside the bounds of an allocated buffer. An attacker can leverage the flaw to crash the application, corrupt data, or execute arbitrary code in the context of the current user.
The attack vector is local and requires user interaction, since a victim must open the malicious file. Autodesk published advisory ADSK-SA-2025-0024 describing the issue and providing fixed releases.
Critical Impact
Successful exploitation allows arbitrary code execution in the context of the user running an affected Autodesk product, with high impact to confidentiality, integrity, and availability.
Affected Products
- Autodesk Shared Components
- Autodesk AutoCAD 2026 and AutoCAD verticals (Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D)
- Autodesk 3ds Max 2026, Advance Steel 2026, Civil 3D 2026, InfraWorks 2026, Inventor 2026, Revit 2026, Revit LT 2026, Vault 2026
Discovery Timeline
- 2025-12-16 - CVE-2025-10900 published to NVD
- 2025-12-19 - Last updated in NVD database
Technical Details for CVE-2025-10900
Vulnerability Analysis
The vulnerability resides in the parsing logic for MODEL files within Autodesk Shared Components, a library used by many Autodesk 2026 desktop applications. When the parser processes a malformed MODEL file, it writes data past the end of an allocated buffer, producing an out-of-bounds write condition. Because Shared Components is reused across the Autodesk product portfolio, a single defective code path exposes 3ds Max, AutoCAD, Revit, Inventor, Civil 3D, and other products simultaneously.
Memory corruption of this class commonly allows an attacker to overwrite adjacent heap metadata, function pointers, or virtual table entries. With deterministic control of the overwritten memory, an attacker can pivot from a crash to arbitrary code execution in the process. The flaw is categorized under [CWE-787] (Out-of-Bounds Write).
Root Cause
The root cause is improper validation of size or offset fields inside the MODEL file structure during deserialization. The parser does not enforce bounds on a destination buffer before performing a write operation, allowing attacker-controlled input to dictate the length or position of the write.
Attack Vector
Exploitation requires social engineering. An attacker delivers a crafted MODEL file through email, a shared project repository, a third-party model marketplace, or a compromised collaboration platform. When the victim opens the file in an affected Autodesk application, the parser triggers the out-of-bounds write. Code executes with the privileges of the logged-in user. No network access to the host is required.
No public proof-of-concept code is available. See the Autodesk Security Advisory ADSK-SA-2025-0024 for vendor-specific technical detail.
Detection Methods for CVE-2025-10900
Indicators of Compromise
- Unexpected crashes or Windows Error Reporting (WerFault.exe) events tied to Autodesk processes such as acad.exe, revit.exe, 3dsmax.exe, or inventor.exe shortly after opening a MODEL file.
- Child processes spawned by Autodesk applications, particularly cmd.exe, powershell.exe, or rundll32.exe, which are uncommon for normal CAD workflows.
- MODEL files arriving from untrusted email senders, external file shares, or unverified third-party content libraries.
Detection Strategies
- Hunt for process lineage where an Autodesk binary is the parent of a scripting or living-off-the-land binary, then correlate with recent file-open activity on .model or related CAD extensions.
- Inspect crash dumps from Autodesk processes for access violations during file parsing functions inside Autodesk Shared Components modules.
- Apply YARA or content-inspection rules at the email gateway and file-sharing tier to flag unusual MODEL files with malformed headers or oversized structural fields.
Monitoring Recommendations
- Monitor endpoint telemetry for anomalous module loads and exception events inside Autodesk processes on engineering workstations.
- Track inventory of installed Autodesk 2026 product versions and alert when hosts remain below the fixed builds documented in ADSK-SA-2025-0024.
- Audit file-share and DMS activity for MODEL files uploaded by external users or accounts outside the engineering organization.
How to Mitigate CVE-2025-10900
Immediate Actions Required
- Apply the updates listed in Autodesk Security Advisory ADSK-SA-2025-0024 to all affected 2026 product installations and the underlying Autodesk Shared Components.
- Restrict opening of MODEL files originating from external or untrusted sources until patching is complete across the engineering fleet.
- Communicate to CAD users that opening unsolicited model files can lead to code execution on their workstation.
Patch Information
Autodesk has released fixed versions for the affected 2026 products. Refer to ADSK-SA-2025-0024 for the exact fixed build numbers per product. Updates are distributed through the Autodesk Access desktop application and the Autodesk Account portal. Apply the Shared Components update along with each affected product, as both are required to fully remediate the parsing flaw.
Workarounds
- Enforce least-privilege user accounts on engineering workstations so that any successful exploitation runs with limited rights rather than administrator privileges.
- Use email and web gateway filters to block or quarantine inbound MODEL files from unknown senders or external domains.
- Validate model files in an isolated sandbox or dedicated virtual machine before importing them into production project environments.
# Verify installed Autodesk product builds on Windows hosts
Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" |
Where-Object { $_.Publisher -like "*Autodesk*" } |
Select-Object DisplayName, DisplayVersion, InstallDate |
Sort-Object DisplayName
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

