An out-of-bounds read in the Windows Search Component allows an authorized local user to read sensitive data from memory that should not be accessible, potentially exposing confidential information. The flaw is categorized as a bounds-checking error that can lead to information leakage rather than arbitrary code execution or privilege escalation. The vulnerability is limited to local exploitation, as only users with sufficient access rights can invoke the Search component to trigger the read operation.

Affected products include Microsoft Windows 10 releases beginning with version 1607 up through 22H2, Microsoft Windows 11 starting at 23H2 through 26H2, and various Windows Server editions from Server 2012 (including Core installations) through Server 2025 and Server 2025 Core. Specific builds such as Windows 10 21H2, 22H2, 11 24H2, 11 25H2, and 11 26H1 are listed among the impacted versions.

The CVSS score of 5.5 indicates a moderate risk, and the EPSS score is not available, so exploitation probability is unknown. The vulnerability is not listed in the CISA KEV catalog, suggesting no confirmed known exploits. The likely attack vector is local, requiring the attacker to have authorized access on the target machine. The impact scope is limited to the compromised user account, with no known ability to affect other accounts or the entire system.