Article
Cybersecurity
Oct 25, 2025
CVE-2025-59287: Critical vulnerability in Windows Server Update Services (WSUS)
CVE-2025-59287 is a critical vulnerability in Windows Server Update Services (WSUS). This article briefly explains the flaw, its potential impact, and how to mitigate it, along with key indicators of compromise (IoCs).
Summary
On October 23, Microsoft released an update for a critical remote command execution vulnerability in Windows Server Update Services (WSUS).
IT administrators use WSUS to centrally distribute Microsoft updates inside networks.
CVE-2025-59287 is a critical vulnerability in WSUS that allows attackers to execute commands remotely without authentication. The vulnerability score is CVSS 9.8.
To exploit the vulnerability, an attacker targets the service ports on TCP/8530 and TCP/8531 and sends specially crafted POST requests to the update service. The service decrypts and deserializes the payload, which can result in command execution.
Command execution occurs via WSUS processes such as wsusservice.exe or w3wp.exe, which may launch cmd.exe or powershell.exe.
What is CVE-2025-59287?
This is a remote command execution (RCE) vulnerability in the WSUS update service caused by unsafe deserialization of a request.
An attacker sends a
POSTrequest to the WSUS web endpoints.The request contains an
AuthorizationCookieobject encrypted with AES-128-CBC.After decryption, the service deserializes the object using .NET’s
BinaryFormatterwithout validating the object type.This unsafe deserialization leads to remote code execution under the SYSTEM account.
Recommendations
1. Apply the Microsoft security update
Install Microsoft’s security update for CVE-2025-59287 immediately. See Microsoft Security Response Center for the official guidance:https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59287
2. Isolate WSUS access
Limit access to WSUS servers to only management machines and other update servers that require communication with WSUS.
Block inbound access to service ports
TCP/8530andTCP/8531from general networks and from the public internet.
Indicators of Compromise (IOCs)
Check WSUS log file:
Look for stack traces or errors such as:
Check IIS logs:
Look for POST requests to WSUS web services, for example:
Windows event / process monitoring
wsusservice.exespawningcmd.exeorpowershell.exe(unexpected — normally it does not spawn child processes).w3wp.exespawningcmd.exeorpowershell.exe.
Sources
HawkTrace:
https://hawktrace.com/blog/CVE-2025-59287-UNAUTHHuntress:
https://www.huntress.com/blog/exploitation-of-windows-server-update-services-remote-code-execution-vulnerabilityMicrosoft Security Response Center (MSRC):
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59287
Ready to Secure and Optimize Your IT?
Book your free 15-minute IT assessment today and discover how to protect and optimize your business technology.
