Windows Search Component EUVD-2026-73510

Exploitation requires an existing local session on the target host with at minimum standard (low-privileged) user credentials - PR:L in the CVSS vector confirms this. No network access is required (AV:L). No user interaction from a second party is needed (UI:N). No non-default configuration is stated as a prerequisite; the Windows Search Component (Windows Search service) is enabled by default on all affected Windows Desktop and Server editions, making this exploitable in default configurations given local access. What limits exploitation: the attacker must already have a valid local session (rules out fully remote, unauthenticated scenarios); the attacker gains only an integrity primitive (no credential or data disclosure, no denial of service available through this vector alone); lateral movement would require chaining with additional techniques.

The CVSS 5.5 Medium score is reasonable and reflects the key limiting factor: AV:L requires an existing local session, substantially reducing the attack surface compared to network-exploitable flaws. PR:L confirms a standard (non-admin) account suffices, so it does not require prior privilege escalation. The impact is integrity-only (I:H, C:N, A:N), meaning an attacker can tamper with search-related data or configurations but cannot read additional confidential material or crash the system through this vector alone. No KEV listing, no public POC, and no EPSS score were provided in the input data, so exploitation probability cannot be quantified. In practice, this vulnerability is most relevant in shared multi-user environments, terminal server farms, or scenarios where insider threat or malware already running under a standard account seeks to tamper with indexed data or search behavior to facilitate further attack steps. The 'Authentication Bypass' tag is a mislabel - this is an authorization bypass (the caller is authenticated; the authorization check is absent), not a bypass of the authentication mechanism itself.

A standard-privilege local user (or malware running under a standard account) sends a crafted API request to the Windows Search Component, triggering the missing authorization code path. Because no authorization check is performed, the operation succeeds and the attacker can modify search index data, configuration entries, or related settings that should be writable only by administrators. This could be used to corrupt search results, hide files from indexed search, or alter application behavior that relies on search functionality.