A maliciously crafted binary file, when present while loading files in certain Autodesk applications, could lead to execution of arbitrary code in the context of the current process due to an untrusted search path being utilized.
The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product’s direct control.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Infrastructure_parts_editor | Autodesk | 2026 (including) | 2026.0.2 (excluding) |
| Inventor | Autodesk | 2026 (including) | 2026.0.2 (excluding) |
| Navisworks_manage | Autodesk | 2026 (including) | 2026.0.2 (excluding) |
| Navisworks_simulate | Autodesk | 2026 (including) | 2026.0.2 (excluding) |
| Revit | Autodesk | 2026 (including) | 2026.0.2 (excluding) |
| Vault | Autodesk | 2026 (including) | 2026.0.2 (excluding) |
This might allow attackers to execute their own programs, access unauthorized data files, or modify configuration in unexpected ways. If the product uses a search path to locate critical resources such as programs, then an attacker could modify that search path to point to a malicious program, which the targeted product would then execute. The problem extends to any type of critical resource that the product trusts. Some of the most common variants of untrusted search path are: