Skip to main content
CVE-2025-10885VulnerabilityPublished Updated

CVE-2025-10885: Autodesk Installer · Execution with Unnecessary Privileges

Affects Autodesk InstallerSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Autodesk InstallerAffected
  • =2.18
Fixed in–

AI-suggested

Until an official patch is released, organizations should implement several targeted mitigations: 1) Restrict local user permissions and limit the number of users with local access to systems running Autodesk Installer 2.18. 2) Employ application whitelisting and binary integrity monitoring to detect and block execution of unauthorized or suspicious installer files. 3) Monitor system and security logs for unusual installer activity or privilege escalation attempts. 4) Use endpoint detection and response (EDR) solutions to identify and contain exploitation attempts quickly. 5) Educate users about the risks of executing untrusted files, especially in environments where Autodesk software is installed. 6) Isolate critical systems running Autodesk software from less secure network segments to reduce exposure. 7) Prepare for rapid deployment of patches once Autodesk releases a fix, including testing in controlled environments to ensure compatibility. 8) Review and harden system configurations to minimize the impact of potential privilege escalations.

Description

A maliciously crafted file, when executed on the victim's machine, can lead to privilege escalation to NT AUTHORITY/SYSTEM due to an insufficient validation of loaded binaries. An attacker with local and low-privilege access could exploit this to execute code as SYSTEM.

References

Community reviews

Loading reviews…