Code execution via malformed CATPART parsing
Published Feb 18, 2026 · Updated Feb 18, 2026
Out-of-bounds write in Autodesk Shared Components 2026.5 and earlier allows attackers to execute code via a crafted CATPART file. Autodesk has not identified the parser routine or disclosed how CATPART data drives the write beyond its intended memory boundary. Opening the file in a dependent Autodesk desktop product is required; successful exploitation runs code in that product's process, while failed attempts can crash it or corrupt data.
Summary
What happened
Out-of-bounds write in Autodesk Shared Components 2026.5 and earlier allows attackers to execute code via a crafted CATPART file. Autodesk has not identified the parser routine or disclosed how CATPART data drives the write beyond its intended memory boundary. Opening the file in a dependent Autodesk desktop product is required; successful exploitation runs code in that product's process, while failed attempts can crash it or corrupt data.
The record
- CVE
- CVE-2026-0874
- Published
- Feb 18, 2026
- Updated
- Feb 18, 2026
- Vendor
- Autodesk
- Product
- Autodesk Shared Components
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2026CVE publishedPublication date reported by the CVE source.
- Feb 18, 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=2026.5 <2026.6
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