Windows Autopilot EUVD-2026-73771

The attacker must hold an existing authenticated local session on the target Windows device using a standard (low-privilege) user account - PR:L confirms this requirement. The device must be running an affected Windows version with Autopilot components present, which is the default state for any enterprise-managed Windows 10/11 or Windows Server 2025/2022 device enrolled via Microsoft Intune or Windows Autopilot. No special configuration, feature flag, or non-default setting is required beyond the device being an Autopilot participant. What limits exploitation: remote unauthenticated access is not possible (AV:L); the attacker cannot escalate to code execution or access confidential data through this path alone (C:N, A:N); and initial local access - whether physical, RDP, or via prior compromise - is a hard prerequisite.

The CVSS 5.5 medium rating is well-calibrated for this vulnerability. The local attack vector and low-privilege requirement mean an attacker must already hold an interactive or remote desktop session on the target device, placing this squarely in the post-compromise or insider-threat category rather than an initial-access path. No EPSS score was provided in the input data, and the absence of a KEV listing and public exploit code confirms there is no evidence of opportunistic or widespread exploitation. The integrity-only impact (I:H) is contextually significant in enterprise environments using Autopilot for fleet provisioning: an attacker who can tamper with Autopilot enrollment state or provisioning configurations could affect device trust posture or redirect a device away from corporate management. The 'Authentication Bypass' tag in the input metadata is a loose semantic fit - CWE-306 describes a function that simply lacks an auth check, which is distinct from bypassing an existing authentication mechanism. EPSS data is absent, and no independent exploit research has been cited, so urgency is driven primarily by patch-cycle hygiene rather than active threat signals.

A standard user account holder on an Autopilot-enrolled corporate laptop invokes a local Autopilot management function directly - via API call or a locally accessible interface - that lacks the expected privilege check. Without needing administrator rights, the attacker modifies the device's Autopilot enrollment profile or provisioning parameters, potentially redirecting the device to an attacker-controlled management tenant on next reset. No public exploit code has been identified, so exploitation currently requires knowledge of the specific unprotected function surface.