Skip to main content
VulnerabilityPublished Updated

CVE-2025-59260: Microsoft Windows Server 2016 · Information Exposure

Affects Microsoft Windows Server 2016Source CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% 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:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Microsoft Windows Server 2016Affected
  • =10.0.14393.0
Fixed in–

AI-suggested

To mitigate CVE-2025-59260, organizations should implement the following specific measures: 1) Restrict local access to Windows Server 2016 failover cluster nodes strictly to trusted administrators and service accounts; 2) Monitor and audit local user activities on cluster nodes to detect unauthorized access attempts; 3) Apply the official security patch from Microsoft immediately once released; 4) If patching is delayed, consider temporarily disabling or limiting failover cluster virtual driver functionality if feasible without disrupting critical services; 5) Employ network segmentation and access controls to minimize the risk of unauthorized local access; 6) Use endpoint detection and response (EDR) tools to identify suspicious local activities related to cluster components; 7) Review cluster configuration and sensitive data exposure policies to ensure minimal sensitive information is accessible to low-privilege users; 8) Educate administrators about the risks of local privilege misuse and enforce strong credential management and multi-factor authentication for local accounts. These targeted actions go beyond generic advice by focusing on local access control and cluster-specific protections.

Description

Exposure of sensitive information to an unauthorized actor in Microsoft Failover Cluster Virtual Driver allows an authorized attacker to disclose information locally.

References

Community reviews

Loading reviews…