Skip to main content
CVE-2025-47979VulnerabilityPublished Updated

CVE-2025-47979: Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) · Sensitive Data in Logs

Affects Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)Source CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

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

What to do

Affected software

ProductAffectedFixed in
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)Affected
  • =10.0.25398.0
Fixed in–

AI-suggested

To mitigate CVE-2025-47979, organizations should implement the following specific measures: 1) Restrict local access to Windows Server 2022 systems running Failover Clustering, ensuring only trusted administrators have access. 2) Audit and monitor access to log files generated by the Failover Cluster service, applying strict file permissions to prevent unauthorized reading. 3) Review and configure logging settings to minimize sensitive data inclusion in logs where feasible, possibly by disabling verbose logging or sensitive data logging if not required. 4) Employ host-based intrusion detection systems (HIDS) to alert on unusual access patterns to log files. 5) Maintain up-to-date system inventories to identify affected Windows Server 2022 Server Core installations and prioritize remediation. 6) Monitor Microsoft security advisories for patches or updates addressing this vulnerability and apply them promptly once available. 7) Consider deploying endpoint protection solutions that can detect and block unauthorized local access attempts. 8) Implement strict role-based access controls (RBAC) and least privilege principles to limit the number of users who can access sensitive logs. These measures go beyond generic advice by focusing on access control, log management, and proactive monitoring specific to the vulnerability context.

Description

Insertion of sensitive information into log file in Windows Failover Cluster allows an authorized attacker to disclose information locally.

References

Community reviews

Loading reviews…