CVE-2025-59186: Microsoft Windows Server 2016 · Information Exposure
Affects Microsoft Windows Server 2016Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2016 | Affected
| Fixed in– |
AI-suggested
Until an official patch is released, organizations should implement the following specific mitigations: 1) Restrict local access to Windows Server 2016 systems to trusted administrators only, minimizing the number of users with local privileges. 2) Enforce the principle of least privilege rigorously, ensuring users and services operate with the minimum necessary permissions to reduce the risk of exploitation. 3) Monitor and audit local user activity and kernel-level access attempts for unusual or unauthorized behavior that could indicate exploitation attempts. 4) Use endpoint detection and response (EDR) tools capable of detecting suspicious kernel-level operations or information disclosure patterns. 5) Isolate critical servers from less trusted network segments to reduce the likelihood of local attackers gaining access. 6) Prepare for rapid deployment of the official patch once available by maintaining up-to-date asset inventories and testing environments. 7) Educate system administrators about the vulnerability and the importance of limiting local access and privileges. These targeted actions go beyond generic advice by focusing on controlling local access and monitoring kernel-level activities, which are crucial given the vulnerability's local attack vector and kernel context.
Description
Exposure of sensitive information to an unauthorized actor in Windows Kernel allows an authorized attacker to disclose information locally.