dbcve.org
Windows Server 2016Operating system · Microsoft

CVE-2025-59184

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 Windows High Availability Services 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 is a local information disclosure vulnerability in Windows High Availability Services. An authorized attacker with local access can exploit the flaw to view sensitive information that should be protected. The vulnerability stems from improper access controls within the High Availability Services component, allowing disclosure of information to a local user who already has some level of authorized access to the system.

MitigationApply the appropriate Microsoft security updates for Windows High Availability Services when available. Until a patch is released, restrict local access to sensitive systems to trusted personnel only and monitor for unusual local account activity.

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 identify the installed Windows Server version and build number
    Affected if The build number falls within these vulnerable 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 High Availability Services is installed
    Run 'Get-WindowsFeature -Name Failover-Clustering' in PowerShell (on Server) or check Services console for 'ClusSvc' service existence
    Affected if The Failover Clustering or High Availability Services feature is installed on the system
  3. Check Cluster service account permissions
    Open Failover Cluster Manager, expand the cluster, go to 'Cluster Core Resources', right-click each resource and select 'Properties' > 'Security' to review who has access
    Affected if Users with limited local access can view cluster configuration or sensitive resources they should not have visibility into
  4. Review Event Viewer for HA service access attempts
    Open Event Viewer, navigate to 'Application and Services Logs' > 'Microsoft' > 'Windows' > 'FailoverClustering' and look for Event ID 1653 or unexpected access events from low-privilege accounts
    Affected if Events indicate information disclosure or unauthorized access attempts to HA service data

The system is affected if it runs a vulnerable Windows Server version within the listed ranges AND has the High Availability Services or Failover Clustering feature installed.

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 appropriate Microsoft security updates for Windows High Availability Services when available. Until a patch is released, restrict local access to sensitive systems to trusted personnel only and monitor for unusual local account activity.

Recommended fix Moderate confidence

Windows Server 2016: security update to build > 10.0.14393.8519 | Windows Server 2019: security update to build >= 10.0.17763.7919 | Windows Server 2022: security update to build >= 10.0.20348.4294 | Windows Server 2022 23h2: security update to build >= 10.0.25398.1913 | Windows Server 2025: securit

  1. Check current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Identify if Windows High Availability Services role is installed via Server Manager
  3. Apply the appropriate Windows security update for your version from Microsoft Update Catalog or Windows Update
  4. Reboot the server after applying the security patch
  5. Verify the patch was applied by checking the installed updates list
Caveat None expected - this is a security patch for an information disclosure vulnerability in Windows High Availability Services

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

Fix this in Windows Server 2016 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59184 — 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-59184 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