CVE-2025-5335
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA maliciously crafted binary file when downloaded could lead to escalation of privileges to NT AUTHORITY/SYSTEM due to an untrusted search path being utilized in the Autodesk Installer application. Exploitation of this vulnerability may lead to code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an untrusted search path vulnerability in the Autodesk Installer application. When processing a maliciously crafted binary file, the installer uses an insecure search path to locate and execute the file, allowing an attacker to hijack the execution flow and achieve code execution with NT AUTHORITY/SYSTEM privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Autodesk Installer versionOpen Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Autodesk*Installer*"} | Select-Object Name, Version' in PowerShell. Also check the installer executable properties (right-click > Details) if you have a local copy.Affected if The displayed version is lower than 2.15 (e.g., 2.14, 2.13, etc.)
-
Determine installer execution contextIdentify where the Autodesk Installer executable is being launched from. Check the current working directory by running 'Get-Location' before launching the installer, or examine the shortcut path if launching from a desktop shortcut.Affected if The installer is launched from a directory that is writable by other users (e.g., network shares, shared folders, USB drives, or world-writable directories)
-
Inspect PATH environment variableRun 'echo $env:PATH' in PowerShell or 'echo %PATH%' in Command Prompt to view the search path directories. Check each directory for permissions using 'Get-Acl <directory> | Format-List'Affected if Any directory in the PATH is writable by untrusted users or the system has weak permissions on installer-related directories
-
Check for pre-existing binaries in common locationsExamine the directory where you intend to run the installer from, plus %TEMP%, %LOCALAPPDATA%, and the installer working directory. Look for unexpected .exe or .dll files with names matching common Windows utilities (e.g., certutil.exe, msiexec.exe).Affected if Unexpected executables exist in directories the installer searches or uses as working directories
You are affected if your Autodesk Installer version is below 2.15 AND you run the installer from a directory or environment where untrusted users can inject malicious binaries into the search path.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.15
Organizations should exercise caution when downloading Autodesk installer files and ensure they originate from official, trusted sources. Until vendor patches are available, implement application whitelisting and restrict write access to directories in the installer search path.
Installer version 2.15 or later
- Verify current Autodesk Installer version by checking the application's 'About' or version information
- Download the Autodesk Installer version 2.15 or later from the official Autodesk website (autodesk.com) or your organization's software distribution point
- Close all Autodesk applications and any running installer processes
- Run the updated installer to apply the fix
- Restart the system if prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5335 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data