dbcve.org
Windows Server 2016Operating system · Microsoft

CVE-2025-59260

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.17763.7919 / 10.0.20348.4294 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This vulnerability in Microsoft Failover Cluster Virtual Driver allows an authorized local attacker to access sensitive information that should be protected. The issue stems from improper access controls within the virtual driver component used by Windows Failover Clustering, enabling information disclosure to users who have local access but should not have visibility into certain cluster data.

MitigationApply the Microsoft security update for CVE-2025-59260 to all affected Windows systems running Failover Clustering. Test failover functionality after patching to ensure cluster services remain operational.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows Server 2016Operating system
Affected:<= 10.0.14393.8519
Windows Server 2019Operating system
Affected:< 10.0.17763.7919
Windows Server 2022Operating system
Affected:< 10.0.20348.4294
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1913
Windows Server 2025Operating system
Affected:<= 10.0.26100.6899

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows Server version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the installed Windows Server version and build number
    Affected if Version falls within any of these affected ranges: Server 2016 <= 10.0.14393.8519, Server 2019 < 10.0.17763.7919, Server 2022 < 10.0.20348.4294, Server 2022 23h2 < 10.0.25398.1913, Server 2025 <= 10.0.26100.6899
  2. Verify Failover Clustering is enabled
    Run 'Get-WindowsFeature -Name Failover-Clustering' in PowerShell or check via Server Manager > Add Roles and Features to see if the Failover Clustering role is installed
    Affected if Failover Clustering role is installed or enabled on the server
  3. Check Failover Clustering virtual driver component
    Run 'Get-ClusterResource -Cluster <your-cluster-name> | Get-ClusterResourceType' or inspect the cluster resource types via Failover Cluster Manager under Roles > Resources, looking for virtual driver components
    Affected if The ClusVirtualDriver or related virtual driver resource type exists in the cluster configuration

The system is affected if it runs an affected Windows Server version AND has Failover Clustering with the virtual driver component enabled, with the OS build number falling within the vulnerable version ranges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.17763.7919 / 10.0.20348.4294 / 10.0.25398.1913 or later
Fixed in 10.0.17763.791910.0.20348.429410.0.25398.1913
Interim mitigation

Apply the Microsoft security update for CVE-2025-59260 to all affected Windows systems running Failover Clustering. Test failover functionality after patching to ensure cluster services remain operational.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2025-59260 (Windows Build numbers: Server 2016 >=10.0.14393.8520, Server 2019 >=10.0.17763.7919, Server 2022 >=10.0.20348.4294, Server 2022 23h2 >=10.0.25398.1913, Server 2025 >=10.0.26100.6900)

  1. Open Settings on the Windows Server machine and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, run 'Get-WindowsUpdate' in PowerShell with admin privileges to check for updates
  4. Ensure the Microsoft Failover Cluster Virtual Driver update (CVE-2025-59260) is installed
  5. Restart the server if prompted to complete the update installation
  6. Verify the installed version matches or exceeds the fixed build number for your Windows Server version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows Server 2016 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59260 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data