CVE-2025-59287CRITICAL · 9.8Patch second

Microsoft Windows Server Update Service (WSUS) Deserialization of Untrusted Data Vulnerability

CVE-2025-59287 is a security vulnerability in Microsoft Windows, added to CISA KEV on October 24, 2025. Patch order: second of four.

Published (added to CISA KEV) · Updated · Microsoft Windows

What is CVE-2025-59287?

Microsoft Windows Server Update Service (WSUS) contains a deserialization of untrusted data vulnerability that allows for remote code execution.

Who is affected by CVE-2025-59287?

Affects anyone running Windows workstations or servers. In a small CPA, legal, or dental practice, Windows is typically the platform your accounting, document management, or practice management software runs on — exploitation gives an attacker access to whatever client files and credentials live on those machines.

What should I do about CVE-2025-59287?

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

The action above is CISA's wording. The directive it names, BOD 22-01, was revoked by BOD 26-04 on June 10, 2026; CISA's catalog still carries the older text for this entry.

If you don't have someone in-house to verify the patch deployed across every endpoint — or you're not sure whether you're affected — that's exactly the kind of triage we do. Request a free review.

Insurance readiness

Your insurer will ask if this is patched.

Unpatched entries on CISA's Known Exploited Vulnerabilities list are exactly what cyber-insurance carrier questionnaires probe for, and knowing which controls they check is how you keep a renewal from stalling.

Get the free carrier questionnaire →

Severity

CVSS base score: 9.8 — CRITICAL

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

Weakness classification: CWE-502

CVSS, severity, and CWE data from the National Vulnerability Database (NVD). This product uses data from the NVD API but is not endorsed or certified by the NVD.

Microsoft fix

  • KB5070883 (Security Update)
  • KB5070884 (Security Update)
  • KB5070892 (Standalone Security Update)
  • KB5070881 (Security Update)
  • KB5070893 (Standalone Security Update)
  • KB5070879 (Security Update)
  • KB5070882 (Security Update)
  • KB5070887 (Security Update)
  • KB5070886 (Security Update)

Microsoft Exploitability Index (assessed at update release): Exploitation More Likely

This CVE is on CISA's Known Exploited Vulnerabilities catalog. Microsoft's index reflects their release-time forecast, not current observed activity, and is not automatically revised upward when exploitation appears later.

Sourced from Microsoft Security Update Guide (CVRF document 2025-Oct).

Vendor workaround

Vendor-published workaround

The following workarounds might be helpful in your situation. In all cases, Microsoft strongly recommends that you install the updates for this vulnerability as soon as possible even if you plan to leave either of these workarounds in place:

If you are unable to install the October 23, 2025 out-of-band update, you can take any of the following actions to be protected against this vulnerability:

  • If the WSUS Server Role is enabled on your server, disable it. Note that clients will no longer receive updates from the server if WSUS is disabled.
  • Block inbound traffic to Ports 8530 and 8531 on the host firewall (as opposed to blocking only at the network/perimeter firewall) to render WSUS non-operational.

Important: Do NOT undo either of these workarounds until after you have installed the update.

Vendor-published mitigation

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability.

The following mitigating factors might be helpful in your situation:

The WSUS Server Role is not enabled by default on Windows servers. Windows servers that do not have the WSUS server role enabled are not vulnerable to this vulnerability. If the WSUS server role is enabled, the server will become vulnerable if the fix is not installed before the WSUS server role is enabled.

A workaround reduces exposure while you patch — it is not a substitute for the update. Install the fix above as soon as you can.

Shown as published by Microsoft (Security Update Guide, CVRF document 2025-Oct); formatting sanitized, content unaltered.

CISA due date

CISA's listed due date: November 14, 2025.

Federal civilian agencies work under CISA's Binding Operational Directive 26-04, which replaced BOD 22-01 on June 10, 2026. It sets the deadline for each affected system by:

  • How exposed that system is to the internet
  • Whether the attack can be automated
  • How much control it gives an attacker

Its table gives catalogued vulnerabilities 3 or 14 days.

None of this binds a private business, but treat the date as a strong recommendation, especially if you handle regulated data (HIPAA, GLBA, ABA model rules).

EPSS

EPSS score: 100.0% — higher than 100% of all scored CVEs.

EPSS estimates the probability of exploitation activity in the next 30 days. Every entry on this site is already confirmed exploited, so read it as relative urgency among the things you still have open, not as permission to wait.

Score dated 2026-10-16, from the FIRST.org Exploit Prediction Scoring System.

Source

This entry comes from CISA's Known Exploited Vulnerabilities catalog, public US-Government data we pull daily. The plain-language framing and the what-to-do guidance above are ours. View the original entry on cisa.gov.

Weekly digest

Get the weekly digest in your inbox.

Drop your email and we send you what changed in your watch each week. If nothing changed, we tell you that too.

Watching: Microsoft