#windows

Improper input validation in Windows Server Update Service allows an unauthorized attacker to execute code over a network.

Incorrect privilege assignment in Windows Hello allows an unauthorized attacker to perform tampering locally.

Exposure of sensitive information to an unauthorized actor in Windows Shell allows an authorized attacker to perform spoofing over a network.

**What privileges could be gained by an attacker who successfully exploited this vulnerability?** An attacker who successfully exploited this vulnerability could gain SYSTEM privileges.

Use after free in Windows Clipboard Server allows an unauthorized attacker to elevate privileges locally.

**According to the CVSS metric, the attack vector is local (AV:L). Why does the CVE title indicate that this is a remote code execution?** The word **Remote** in the title refers to the location of the attacker. This type of exploit is sometimes referred to as Arbitrary Code Execution (ACE). The attack itself is carried out locally. This means an attacker or victim needs to execute code from the local machine to exploit the vulnerability.

Improper access control in Windows Client-Side Caching (CSC) Service allows an authorized attacker to disclose information locally.

Generation of error message containing sensitive information in Windows Kernel allows an authorized attacker to disclose information locally.

Heap-based buffer overflow in Windows Media allows an unauthorized attacker to execute code locally.

**Are there additional steps I need to take to be protected from this vulnerability?** Admins should take the following steps to be protected from CVE-2026-0386: 1. Audit existing WDS usage and identify hands-free deployments. 2. Opt in for protection by configuring the registry settings described in: Windows Deployment Services (WDS) Hands-Free Deployment Hardening Guidance. This will provide immediate protection. This security protection will be enabled by default in a future security update release and no additional administrator action will be required. **How is Microsoft addressing this vulnerability?** To address this vulnerability, by default the hands-free deployment feature will not be supported beginning with a security update in a future release in mid-2026. **Why is the WDS Unattended Installation feature being deprecated?** The legacy WDS workflow transmits unattend.xml over unauthenticated RPC, exposing sensitive credentials during PXE boot. This creates a securi...