Code execution via unchecked PRT file data
Published Sep 22, 2025 · Updated Sep 22, 2025
Memory corruption in Autodesk Shared Components 2026.3 allows context-dependent attackers to execute code via a crafted PRT file. The PRT parser fails to validate user-supplied file data before copying it into a bounded buffer, corrupting process memory. A target must open the file or visit a malicious page; successful exploitation runs code with the privileges of the current Autodesk process.
Summary
What happened
Memory corruption in Autodesk Shared Components 2026.3 allows context-dependent attackers to execute code via a crafted PRT file. The PRT parser fails to validate user-supplied file data before copying it into a bounded buffer, corrupting process memory. A target must open the file or visit a malicious page; successful exploitation runs code with the privileges of the current Autodesk process.
The record
- CVE
- CVE-2025-8892
- Published
- Sep 22, 2025
- Updated
- Sep 22, 2025
- Vendor
- Autodesk
- Product
- Autodesk Shared Components
- Classifications
- CWE-120, CAPEC-100, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2025CVE publishedPublication date reported by the CVE source.
- Sep 22, 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.1 <2026.4
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