Windows Kernel EUVD-2026-99083

Exploitation requires the attacker to already have local, authenticated access to the Windows host with at least low-level privileges (PR:L) - it cannot be triggered remotely or by an unauthenticated user. No special non-default configuration is indicated by the description; the flaw resides in the Windows Kernel itself, which is present by default on all listed Windows and Windows Server editions (including Server Core installations). The limiting factors are the need for prior local code-execution/account access and that the impact is confined to information disclosure (no integrity or availability effect), so it is realistically a post-foothold capability rather than an initial-access vector.

This is a genuine but moderate-priority issue, consistent with its 5.5 (Medium) CVSS score rather than a high-urgency flaw. The CVSS vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N shows a LOCAL attack vector requiring already-present low privileges (PR:L, an authorized attacker), with no integrity or availability impact and only confidentiality at stake - characteristic of CWE-497 (exposure of sensitive system information). There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score was supplied in the input, so there is no signal of active or probable exploitation. The practical risk is as a post-compromise / local privilege-context information leak (e.g. leaking kernel memory or system data that aids a further exploit chain) rather than a remote entry point. Signals are internally consistent: a local, authenticated, confidentiality-only bug with no exploitation evidence does not warrant emergency patching but should be remediated in normal Patch Tuesday cadence given the enormous Windows install base.

A low-privileged local user or a process already running with limited rights on an affected Windows host invokes the vulnerable kernel interface to read sensitive system information it should not be able to access. The disclosed data (such as kernel memory contents or address layout) could then be used to defeat mitigations and strengthen a separate local privilege-escalation chain. No public proof-of-concept exploit has been identified at time of analysis.