Code execution via out-of-bounds RCS parser write
Published Apr 15, 2025 · Updated Feb 26, 2026
Out-of-bounds write in Autodesk desktop products 2023 through 2025 allows attackers to execute code through a crafted RCS file. The RCS parser writes beyond an allocated memory boundary while processing attacker-controlled file content; Autodesk has not disclosed the specific routine or malformed field. Exploitation requires a user to open the file and can execute code in the current process, corrupt data, or crash the application.
Summary
What happened
Out-of-bounds write in Autodesk desktop products 2023 through 2025 allows attackers to execute code through a crafted RCS file. The RCS parser writes beyond an allocated memory boundary while processing attacker-controlled file content; Autodesk has not disclosed the specific routine or malformed field. Exploitation requires a user to open the file and can execute code in the current process, corrupt data, or crash the application.
The record
- CVE
- CVE-2025-1274
- Published
- Apr 15, 2025
- Updated
- Feb 26, 2026
- Vendor
- Autodesk
- Product
- AutoCAD Mechanical
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 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=2023 <2023.1.8
- Affected versionversion=2024 <2024.1.8
- Affected versionversion=2025 <2025.1.3
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.
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