dbcve.org
Windows Server 2022 23h2Operating system · Microsoft

CVE-2025-47979

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.25398.1913 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
Insertion of sensitive information into log file in Windows Failover Cluster 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

Windows Failover Cluster writes sensitive information to log files that can be read by an authorized local attacker, leading to information disclosure. The vulnerability stems from improper handling of sensitive data in the clustering component's logging mechanism.

MitigationApply Microsoft security updates for Windows Failover Cluster when available, and immediately review existing cluster logs for exposed sensitive information to determine if exploitation has occurred.

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 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. Confirm Failover Clustering is installed
    Run 'Get-WindowsFeature -Name Failover-Clustering' in PowerShell on the target server. If the feature is installed, InstallState will show 'Installed'.
    Affected if Failover Clustering feature is installed and the Windows version is within the affected ranges
  2. Check Windows Server version
    Run 'winver' or 'Get-ComputerInfo | Select-Object WindowsVersion, OsVersion' to obtain the exact build number. Compare against: Windows Server 2022 23h2 build < 10.0.25398.1913, or Windows Server 2025 build <= 10.0.26100.6899.
    Affected if The Windows build number falls within either of the affected version ranges
  3. Locate Failover Cluster log files
    Run 'Get-ClusterLog -DestinationPath C:\ClusterLogs' to generate cluster logs, or navigate to the default log location typically at %SystemRoot%\Cluster\Reports\. Verify these files exist.
    Affected if Cluster log files exist on the system
  4. Inspect cluster logs for sensitive information
    Open generated cluster log files using a text editor or run 'Select-String -Path C:\ClusterLogs\*.log -Pattern "password|secret|credential|key" -Recurse' to search for sensitive keywords that should not have been logged.
    Affected if Log files contain sensitive data such as passwords, secrets, credentials, or keys that should not have been written to log output

A system is affected if it runs Windows Server 2022 23h2 or Windows Server 2025 with the Failover Clustering feature enabled and within the specified build ranges, and contains cluster logs with improperly disclosed sensitive information.

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.25398.1913 or later
Fixed in 10.0.25398.1913
Interim mitigation

Apply Microsoft security updates for Windows Failover Cluster when available, and immediately review existing cluster logs for exposed sensitive information to determine if exploitation has occurred.

Recommended fix High confidence

Windows Server 2022 23h2: build 10.0.25398.1913 or later | Windows Server 2025: build 10.0.26100.6900 or later

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Update & Security > Windows Update, or use WSUS/SCCM in enterprise environments
  3. Search for and install the latest Windows security updates that address this vulnerability
  4. Restart the server as prompted to complete the installation
  5. Verify the installed version matches or exceeds 10.0.25398.1913 for Windows Server 2022 23h2, or 10.0.26100.6900 for Windows Server 2025
Caveat Standard Windows update; review release notes for any cluster-specific considerations before applying in production

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

Fix this in Windows Server 2022 23h2 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-47979 — 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-47979 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