CVE Tools
Track your stack

CVE-2025-59287

Windows Server Update Service (WSUS) Remote Code Execution Vulnerability

Exploited in the wild. In CISA KEV since 2025‑10‑24. Fixed versions are out.

CVSS 3.19.8CriticalEPSS percentile99th100% chance in 30 daysCISA KEVListedsince 2025-10-24, due 2025-11-14
No public exploit knownFix5 products6 fixed builds listed below

Published Updated Sources: CVE.org, NVD, BDU, CSAF

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Microsoft Windows Server 2012Affected: ≥ 6.2.9200.0, < 6.2.9200.25728Upgrade to: 6.2.9200.25728Stated by: CVE record
  • Microsoft Windows Server 2012 R2Affected: ≥ 6.3.9600.0, < 6.3.9600.22826Upgrade to: 6.3.9600.22826Stated by: CVE record
  • Microsoft Windows Server 2016Affected: ≥ 10.0.14393.0, < 10.0.14393.8524Upgrade to: 10.0.14393.8524Stated by: CVE record
  • Microsoft Windows Server 2019Affected: ≥ 10.0.17763.0, < 10.0.17763.7922Upgrade to: 10.0.17763.7922Stated by: CVE record
  • Microsoft Windows Server 2022Affected: ≥ 10.0.20348.0, < 10.0.20348.4297Upgrade to: 10.0.20348.4297Affected: ≥ 10.0.25398.0, < 10.0.25398.1916Upgrade to: 10.0.25398.1916Stated by: CVE record

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

Check it yourselfA free Nuclei and OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Discuss checks for your systems with a specialist. Scope is agreed before testing.

Coverage timeline

2 publishers

  1. Vendor patch released

    ·Daily CyberSecurity (securityonline.info)

  2. Technical analysis published

    ·Positive Technologies (Хабр)

  3. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened. 1 further article named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

We strongly recommend the following industry cybersecurity best practices. * Locate control and safety system networks and remote devices behind firewalls and isolate them from the business network. * Install physical controls so no unauthorized personnel can access your industrial control and safety systems, components, peripheral equipment, and networks. * Place all controllers in locked cabinets and never leave them in the “Program” mode. * Never connect programming software to any network other than the network intended for that device. * Scan all methods of mobile data exchange with the isolated network such as CDs, USB drives, etc. before use in the terminals or any node connected to these networks. * Never allow mobile devices that have connected to any other network besides the intended network to connect to the safety or control networks without proper sanitation. * Minimize network exposure for all control system devices and systems and ensure that they are not accessible from the Internet. * When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices. For more information refer to the Schneider Electric [Recommended Cybersecurity Best Practices](https://www.se.com/us/en/download/document/7EN52-0390/) document.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2025-10-24.

US federal agencies must remediate by 2025-11-14.

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

100% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

10 events over 254 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. EPSS band changehigh → critical
  3. Nuclei check added
  4. Patch availableworkaround available, record updated
  5. Added to CISA KEV
  6. Publishedweakness classified, att&ck mapped

Affected products

And 25 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 16 more references. See all after sign-in

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory. This one: actively exploited.