Code execution via unvalidated SLDPRT parsing
Published Mar 13, 2025 · Updated Feb 26, 2026
Memory corruption in affected Autodesk AutoCAD 2022–2025 releases allows attackers to execute code via a crafted SLDPRT file. The SLDPRT parser fails to validate user-supplied file data before processing it, producing memory corruption in the current process. Exploitation requires a user to visit a malicious page or open the file, and resulting code runs with that user's process privileges.
Summary
What happened
Memory corruption in affected Autodesk AutoCAD 2022–2025 releases allows attackers to execute code via a crafted SLDPRT file. The SLDPRT parser fails to validate user-supplied file data before processing it, producing memory corruption in the current process. Exploitation requires a user to visit a malicious page or open the file, and resulting code runs with that user's process privileges.
The record
- CVE
- CVE-2025-1430
- Published
- Mar 13, 2025
- Updated
- Feb 26, 2026
- Vendor
- Autodesk
- Product
- AutoCAD Mechanical
- Classifications
- CWE-120, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=2022 <2022.1.6
- Affected versionversion=2023 <2023.1.7
- Affected versionversion=2024 <2024.1.7
- Affected versionversion=2025 <2025.1.2
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