Windows Search EUVD-2026-73680

A valid local authenticated user account is required (PR:L per CVSS vector) - remote unauthenticated exploitation is not possible. The attacker must have an interactive or programmatic session on the target host capable of invoking Windows Search Component functionality with attacker-controlled path input. No secondary user interaction is required (UI:N). Windows Search is enabled and running by default on all affected Windows 11 and Windows Server with desktop experience installations, so no non-default configuration is needed to expose the attack surface. Exploitation is bounded by local access only (AV:L): an attacker must first establish a foothold via another means before leveraging this flaw for privilege escalation.

The CVSS 7.8 score accurately reflects a high-impact local privilege escalation with low attack complexity and no user interaction required. The local attack vector (AV:L) is the primary limiting factor - remote unauthenticated exploitation is not possible. However, LPE flaws with AC:L/PR:L/UI:N are precisely the class of vulnerability most frequently chained after an initial foothold in ransomware and APT intrusions, making the absence of a network vector less reassuring in practice. No public exploit code has been confirmed and the vulnerability is not listed in CISA KEV, but EPSS data is absent from available intelligence, so exploitation probability cannot be quantified. The C:H/I:H/A:H impact triple indicates complete system compromise upon success. Given that Windows Search is enabled by default across affected Windows 11 and Server deployments, the attack surface is broad within any environment where an adversary already holds a low-privileged account - even a mid-sized IT organization should not deprioritize this patch cycle on account of the local-only vector.

An attacker who has obtained a low-privileged local session - through credential phishing, lateral movement, or exploitation of a separate vulnerability - calls into the Windows Search Component with a crafted absolute path targeting a privileged directory such as a system DLL load path or a service binary location. The component processes the attacker-controlled path without enforcing directory boundaries, allowing the attacker to overwrite a file that executes in a SYSTEM context, thereby escalating to full administrative control. No public exploit code has been confirmed, but the low complexity (AC:L) and absence of required user interaction make this technically straightforward for an attacker already on the system.