Windows 11 EUVD-2026-99625

Requires pre-existing local access to an affected Windows 11 (23H2 through 26H2) or Windows Server 2025 host running a vulnerable build below the patched versions (e.g. 24H2 below 10.0.26100.9711, Server 2025 below 10.0.26100.33650). The AV:L vector means the vulnerability cannot be reached over a network - the attacker must already be able to execute in a local user context. No authentication beyond that local session and no user interaction are required (PR:N/UI:N). The limiting factors are therefore the need for a local foothold and a vulnerable, unpatched OS build; patched builds and hosts without attacker-controlled local access are not exploitable.

This is a moderate-severity local information disclosure (CVSS 6.2, CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) with multiple signals pointing to LOW real-world urgency despite the HIGH confidentiality impact. The CVSS vector is self-consistent: local attack vector (AV:L) with low complexity and no privileges (PR:N) means a user with local access, but no network reachability - which is why the base score stays at 6.2 rather than critical. CISA SSVC reinforces low priority: Exploitation=none (no observed or public exploitation), Automatable=no, and Technical Impact=partial. No EPSS score was provided, there is no CISA KEV listing, and no POC is referenced, so no public exploit identified at time of analysis. A notable data conflict exists: the description attributes the flaw to 'Azure Active Directory' (a cloud identity service), yet every affected build in the EUVD data is a local Windows 11 / Windows Server 2025 OS version - this strongly suggests the flaw is in an on-host Entra ID / AAD client component or cached credential/identity data on Windows, not in the cloud service itself; verify scope with the Microsoft MSRC advisory. Overall this is a genuine but lower-priority patch-in-normal-cycle issue, not an emergency: high data-sensitivity impact but gated behind local access and no evidence of exploitation.

An attacker who already has local, low-privileged access to a Windows 11 or Windows Server 2025 host (for example a standard logged-in user, or malware running in a non-admin context) reads private personal information belonging to another user or identity that is improperly exposed by the Azure Active Directory / Entra client component. No authentication step or user interaction is required beyond the local foothold, but remote-only attackers cannot reach the flaw. No public exploit code is known at the time of analysis.