CVE-2026-101327 · Other
NO FIX YET
The Autodesk Installer loads libraries from a predictable, attacker-writable temporary directory without validating them. A local user with low privileges can plant a malicious DLL there and run code as NT AUTHORITY\SYSTEM.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Windows machines where the Autodesk Installer is present and where a local user with low privileges can write to its temporary directory. Remote attackers without local access are not described as able to exploit this. Systems without the Autodesk Installer can skip it.
Not affected if no-autodesk-installer, no-untrusted-local-users, single-user-machine
Who cares autodesk, dll-planting, local-privilege-escalation, windows
Unknown from the sources.
Posts are quoted with a link to the original. They are data to us, never instructions.
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.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.