CVE
Autodesk Installer privilege escalation via untrusted DLL search path
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 2.26.0.515
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.26.0.515.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A flaw in the Autodesk Installer lets someone with local, low-privilege access gain SYSTEM-level control of the machine. They would do this by placing a malicious DLL in a predictable, attacker-writable temporary directory that the installer loads, which lets them run arbitrary code with SYSTEM rights.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
A maliciously crafted DLL placed in a predictable, attacker-writable temporary directory used by the Autodesk Installer can lead to privilege escalation to NT AUTHORITY\SYSTEM due to insufficient validation of loaded libraries. An attacker with local and low-privilege access could exploit this vulnerability to execute arbitrary code as SYSTEM.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 7.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.26.0.515.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-101327 (Privilege Escalation Vulnerability in Autodesk Installer), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-101327 (entry last updated 2026-11-17):
Affected:
- Autodesk Installer: from 2.22.0.548, fixed in 2.26.0.515
Fixed versions: 2.26.0.515.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-101327 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-101327 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.autodesk.com/trust/security-advisories/adsk-sa-2026-0020
- https://emsfs.autodesk.com/utility/odis/1/installer/latest/AdODIS-installer.exe
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-101327
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-101327"}.Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- Autodesk Installer
From 2.22.0.548 · fixed in 2.26.0.515
Evidence 4
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Patch
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-101327
Is CVE-2026-101327 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-101327?
Installer: from 2.22.0.548 before 2.26.0.515.Source: cve.now feed data
How do I fix CVE-2026-101327?
Upgrade to a fixed version: 2.26.0.515.Source: cve.now feed data