Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-59287: Unauthenticated Remote Code Execution in Microsoft WSUS

Published Oct 14, 2025 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days10 mentions · peak 6 in a dayToday
CVSS9.8Critical · v3.1
EPSS100.0%100th percentile
CISA KEVYesAdded Oct 24, 2025
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2025-59287CWE-502 · Deserialization of Untrusted Data

CVE-2025-59287 is an untrusted-data deserialization vulnerability in Microsoft Windows Server Update Services (WSUS). The WSUS reporting web service processes attacker-controlled serialized data embedded in specially crafted SOAP/XML events. The vulnerable processing involves the ReportEventBatch operation and synchronization-error data supplied through the SynchronizationUpdateErrorsKey field, reaching SoapFormatter deserialization. An unauthenticated attacker with network access to a vulnerable WSUS service can execute arbitrary code with SYSTEM privileges without user interaction. The original October 2025 Patch Tuesday fix was insufficient; Microsoft released an additional out-of-band fix on October 23, 2025. Exploitation in the wild has been observed.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality, integrity, and availability of the WSUS server through arbitrary code execution as SYSTEM. Attackers can access sensitive information, modify server configuration, install malware, establish persistence, and use the server as a foothold for lateral movement. Control of centralized update infrastructure also creates the potential to distribute malicious updates to connected clients and expand compromise across the environment. Observed post-exploitation activity includes interactive reverse shells and ShadowPad deployment; these are follow-on actions rather than intrinsic capabilities of the vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Remove direct internet exposure of WSUS and restrict access to intended internal clients and administration systems. Restrict inbound TCP ports 8530 and 8531, along with any custom WSUS listening ports, using firewall rules and network segmentation. If immediate patching is not possible, temporarily disable the WSUS Server Role. Monitor for unexpected shells, script interpreters, download utilities, and unusual outbound connections originating from WSUS or its IIS worker processes. These measures do not replace installation of the out-of-band fix or a superseding update.

Remediation

Patch, then assume compromise.

Install the applicable Microsoft October 23, 2025 out-of-band security update or a later superseding update that includes the fix. Do not rely solely on the original October 2025 Patch Tuesday update. Applicable update identifiers include KB5070881, KB5070884, and KB5070893, depending on the Windows Server product and servicing channel; select the appropriate package using Microsoft's product-specific guidance. The fix temporarily removes WSUS synchronization error-detail reporting, so the absence of those details after updating is an expected security-related behavior.

Public exploits

Exploits

16 exploits validated by Mallory's analysis. Hidden: 10 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
wsus_deserialization_rce.rbThis repository contains a single Metasploit module (modules/exploits/windows/http/wsus_deserialization_rce.rb) that exploits a deserialization vulnerability (CVE-2025-59287) in Microsoft Windows Server Update Services (WSUS). The exploit targets the legacy serialization mechanism in WSUS, allowing an unauthenticated attacker to send specially crafted SOAP requests to various WSUS web service endpoints. The module interacts with three main SOAP endpoints: ReportingWebService.asmx, SimpleAuth.asmx, and Client.asmx, to gather necessary tokens and parameters before sending a maliciously crafted event that triggers unsafe .NET deserialization. Upon successful exploitation, arbitrary code is executed as administrator on the WSUS server. The module is operational and provides a customizable payload, leveraging Metasploit's .NET deserialization utilities. The code is written in Ruby and is structured as a standard Metasploit exploit module, with clear separation of functions for each stage of the attack.Disclosed Oct 14, 2025 · Framework: metasploit · ruby · networkWeaponizedCVE-2025-59287This repository contains a Python exploit for CVE-2025-59287, a critical remote code execution vulnerability in Microsoft Windows Server Update Services (WSUS). The exploit targets the GetCookie() endpoint, which is vulnerable to unsafe deserialization of AuthorizationCookie objects. The repository consists of two files: a README.md that explains the vulnerability and a Python script (cve-2025-59287-exp.py) that automates the exploitation process. The script interacts with several WSUS SOAP endpoints, including /SimpleAuthWebService/SimpleAuth.asmx, /ReportingWebService/ReportingWebService.asmx, and /ClientWebService/Client.asmx, to obtain necessary cookies and send a malicious payload. If successful, the exploit achieves remote code execution as SYSTEM on the target WSUS server. The code is operational and automates the full exploitation chain, requiring only the target URL as input.jiansiting · Disclosed Oct 25, 2025 · python · networkOperationalCVE-2025-59287This repository contains a fully automated exploit for CVE-2025-59287, a critical unauthenticated remote code execution vulnerability in Microsoft Windows Server Update Services (WSUS). The main file, CVE-2025-59287.py, is a Python 3 script that orchestrates the attack. It auto-downloads the ysoserial.NET tool (from a GitHub release) to generate a malicious .NET payload, which is then encrypted using hardcoded WSUS AES keys. The exploit crafts a SOAP request and sends it to the WSUS ClientWebService endpoint (typically at http://target:8530/ClientWebService/Client.asmx), triggering code execution on the server. The payload is a PowerShell reverse shell that connects back to the attacker's specified IP and port, granting SYSTEM-level access. The script includes a built-in listener for the reverse shell, but can also be used with an external listener (e.g., netcat). The repository also includes a README.md with detailed usage instructions and a requirements.txt listing Python dependencies. The exploit is operational and provides a working RCE chain, but is not part of a larger framework.garvitv14 · Disclosed Oct 25, 2025 · python · networkOperationalCVE-2025-59287-WSUSThis repository contains a PowerShell proof-of-concept exploit for CVE-2025-59287, a remote code execution vulnerability in Microsoft WSUS (Windows Server Update Services). The main script, wsus-rce.ps1, automates the exploitation process by interacting with several WSUS SOAP web service endpoints to obtain necessary authentication tokens and then delivers a malicious serialized .NET payload (generated using ysoserial.net) to the server. The payload is a PowerShell-encoded reverse shell that connects back to the attacker's machine. The exploit is triggered when the WSUS console is opened, at which point the reverse shell is executed. The README provides usage instructions and notes that the exploit was tested on Windows Server 2022 with WSUS version 10.0.20348.1. The repository structure is simple, with the main exploit logic contained in a single PowerShell script, and no extraneous files beyond a README and .gitignore.tecxx · Disclosed Oct 27, 2025 · powershell · networkOperationalCVE-2025-59287This repository provides an exploit for CVE-2025-59287, a vulnerability in Microsoft WSUS that allows remote code execution via a logic flaw in WSUS components. The exploit works by sending a crafted payload (using ysoserial.net) to the target WSUS server, which, when the WSUS management console is opened by an administrator, triggers the injection of a memory-resident webshell (WolfShell) or an ASPX webshell. The payloads are provided as serialized .NET objects in the files 'wolfshell.txt' (memory shell), 'wolfaspx.txt' (ASPX webshell), and 'allow7556.txt' (firewall rule to open port 7556). The README.md contains detailed usage instructions, example commands, and screenshots demonstrating successful exploitation and shell access. The exploit enables persistent remote access and arbitrary command execution on the target server. The repository is structured with a README and three payload files, and is intended for security research and defense purposes.0x7556 · Disclosed Oct 30, 2025 · binary (serialized .NET) · ASPX · networkOperationalPoC-CVE-collectionThis repository is a PoC collection for several recent critical CVEs, with a focus here on CVE-2025-11953 (React Native Community CLI Metro Development Server RCE). The exploit targets the '/open-url' HTTP endpoint exposed by the Metro server, which is vulnerable to OS command injection due to unsanitized input passed to the Node.js 'open' package. The repository includes both a simple Bash PoC (exploit-basic.sh) and a full-featured Python exploitation framework (exploit-advanced.py). The Python tool supports single command execution, interactive mode, reverse shell deployment (PowerShell for Windows), and file upload (Windows). The exploit is operational and can be used against Windows, Linux, and MacOS targets, provided the vulnerable Metro server is accessible over the network. The main attack vector is unauthenticated network access to the Metro server's '/open-url' endpoint (typically on port 8081). The repository is well-documented, with detailed usage instructions, mitigation advice, and detection guidance. No hardcoded IPs or domains are present; the exploit is designed to be used against user-specified targets.N3k0t-dev · Disclosed Nov 10, 2025 · python · bash · networkOperationalPoC-CVE-collectionRepository is a small “PoC CVE collection” with 3 CVE folders referenced, but only CVE-2025-11953 contains actual exploit code in the provided archive (Python + Bash). The other two CVEs (CVE-2025-59287 WSUS deserialization RCE and CVE-2025-8941 Linux-PAM pam_namespace privesc) are documentation-only here (READMEs describe additional scripts like wsus-exploit.py/pam-exploit.c, but those files are not present in the provided file list). CVE-2025-11953 exploit purpose/structure: - Target: React Native Community CLI Metro development server exposing an `open-url` HTTP endpoint. - Primitive: unauthenticated network OS command injection by POSTing JSON to `/open-url` with a crafted `url` value. - Files: - `CVE-2025-11953/exploit-basic.sh`: minimal PoC that checks reachability (GET /) then POSTs to `$TARGET/open-url` with `{"url":"$COMMAND"}`; treats HTTP 200/204 as success. - `CVE-2025-11953/exploit-advanced.py`: a more featureful exploitation tool using `requests.Session()`. - `test_connectivity()` performs GET to base target URL. - `execute_command()` posts to `{target}/open-url` and supports OS selection; Windows wraps commands with `cmd /c`. - `upload_file()` reads a local file, base64-encodes it, and writes it to an arbitrary remote path via an inlined PowerShell `WriteAllBytes` command (Windows-only). - `get_reverse_shell()` sends an inlined PowerShell reverse shell that connects back to attacker-supplied `--lhost` and `--lport` (default 4444). Output is effectively blind (no command output parsing), consistent with the README warning. Notable fingerprintable network targets/endpoints: - HTTP endpoint `/open-url` on the Metro server (commonly port 8081) is the key exploit surface. - Reverse shell callback is to attacker-controlled TCP `lhost:lport` (default port 4444). Overall, this repo is primarily an operational RCE PoC/tooling for CVE-2025-11953, packaged alongside documentation for two additional CVEs that are not actually implemented in the provided code snapshot.GhoStZA-debug · Disclosed Nov 11, 2025 · python · bash · network · local (described only; no code present)Operationalcve-2025-59287This repository is a Python-based exploitation toolkit for CVE-2025-59287, a remote code execution vulnerability in Microsoft Windows Server Update Services (WSUS). The toolkit consists of two main modules: 1. cve-2025-59287-encr.py: An encryption utility that generates AES-encrypted, .NET-serialized payloads containing arbitrary system commands. It supports both legacy and secure encryption modes and allows for custom keys and output files. 2. cve-2025-59287-exp.py: The main exploit module, which targets a specified WSUS server (typically on port 8530) and delivers the encrypted payload via a crafted SOAP request to the WSUS ReportingWebService endpoint. It includes robust error handling, retry logic, and user-agent rotation to evade detection. The exploit can use a default or custom payload and provides options for timeout and retries. The exploit achieves remote code execution on the WSUS server by leveraging the vulnerability to execute arbitrary commands provided by the attacker. The README provides detailed usage instructions, including example commands and options. The repository is structured with clear separation between payload generation and exploitation logic, and includes a requirements.txt for dependencies. No hardcoded IPs or domains are present in the code, but several example endpoints are provided in the documentation. The exploit is operational and suitable for authorized penetration testing or research in controlled environments.Adel-kaka-dz · Disclosed Nov 21, 2025 · python · networkOperationalCVE-2025-59287---WSUS-SCCM-RCERepository contains a single Python exploit script (CVE-2025-59287.py) plus a short README with references. The script is an operational remote-code-execution exploit targeting Microsoft WSUS/SCCM WSUS web services via SOAP. It (1) generates a .NET deserialization payload on the fly by invoking a local ysoserial.net binary (ysoserial.exe) using the DataSet gadget and SoapFormatter, embedding an attacker-supplied command; (2) interacts with WSUS SOAP endpoints to obtain required identifiers/cookies (ServerId via ReportingWebService.asmx, AuthorizationCookie via SimpleAuth.asmx, then a reporting cookie via Client.asmx); and (3) submits a malicious event (function shown as send_malicious_event in the script, truncated in provided content) that carries the serialized payload, resulting in command execution on the WSUS server. The exploit is network-based, uses requests with TLS verification disabled, and is driven via CLI arguments: target URL, command, and optional ysoserial.exe path.LuemmelSec · Disclosed Jan 16, 2026 · python · network (remote) via SOAP over HTTP/HTTPS to WSUS web services; unauth/auth cookie acquisition then malicious event submission leading to deserialization-based RCEOperationalWSUS-CVE-2025-59287Repository contains a single PowerShell exploit script (WSUS-CVE-2025-59287.ps1) plus a minimal README. Core capability: network-based RCE against a WSUS server by interacting with WSUS SOAP .asmx services to obtain required identifiers/cookies and then delivering a .NET BinaryFormatter deserialization payload. The payload ultimately runs a hidden PowerShell command that establishes an interactive TCP reverse shell to an operator-controlled host/port. High-level flow implemented in the script: - New-Payload: builds a PowerShell TCP reverse shell one-liner, base64-encodes it (Unicode), and uses a local ysoserial.net binary (./ysoserial/ysoserial.exe) to wrap it into a BinaryFormatter payload using the RolePrincipal gadget chain. - Get-ServerId: POSTs SOAP to /ReportingWebService/ReportingWebService.asmx (GetRollupConfiguration) and parses the ServerId from the XML response. - Get-AuthCookie: POSTs SOAP to /SimpleAuthWebService/SimpleAuth.asmx (GetAuthorizationCookie) using ServerId and a provided dnsName/computer object, extracting CookieData. - Get-ReportingCookie: POSTs SOAP to /ClientWebService/Client.asmx (GetCookie) using the authorization cookie to obtain another cookie used for subsequent actions. - Invoke-Exploit (present but truncated in provided content): uses the reporting cookie and serialized payload to deliver the exploit; Invoke-Script orchestrates the full chain and prints success indicators including eventInstanceId and targetSid. Notable observables/endpoints: - WSUS SOAP endpoints: /ReportingWebService/ReportingWebService.asmx, /SimpleAuthWebService/SimpleAuth.asmx, /ClientWebService/Client.asmx over HTTP (default port 8530). - Reverse shell callback: configurable $ncHost/$ncPort (example 10.0.0.100:4444). - Local dependency: ./ysoserial/ysoserial.exe. Overall purpose: provide an operational PoC-style exploit that automates pre-exploitation SOAP interactions and delivers a deserialization-based payload to gain a remote shell on a WSUS server.ross-ns · Disclosed Feb 18, 2026 · powershell · networkOperationalCVE-2025-59287-Exercise-UseRepository contains a 4-step PowerShell exploit chain for CVE-2025-59287 (WSUS unauthenticated RCE) plus a README and gitignore. The workflow is: 1) 1-check.ps1 (vulnerability validation): Sends SOAP requests to WSUS endpoints to confirm (a) SimpleAuthWebService issues authorization cookies to anonymous clients and (b) ReportingWebService is reachable. If both succeed, target is considered vulnerable. 2) 2-generate.ps1 (payload generation): Uses a local ysoserial.net binary (ysoserial.exe) to generate a .NET BinaryFormatter deserialization payload using the RolePrincipal gadget chain, output as base64. Two modes are supported: - filedrop: executes cmd to write a proof file to C:\Windows\Temp\wsus_pwned.txt. - shell: builds a PowerShell TCP reverse shell to LHost:LPort, base64-encodes it, and wraps it in a hidden powershell.exe invocation. The resulting blob is saved to .\blob.txt. 3) 3-deliver.ps1 (unauthenticated delivery/injection): Performs the exploitation chain over SOAP: - Requests an anonymous auth token from /SimpleAuthWebService/SimpleAuth.asmx (GetAuthorizationCookie). - Exchanges it for a reporting session cookie via /ClientWebService/Client.asmx (GetCookie), extracting Expiration and EncryptedData. - Injects the serialized payload by calling /ReportingWebService/ReportingWebService.asmx (ReportEventBatch), embedding the base64 blob into the ReportingEvent ExtendedData MiscData field as SynchronizationUpdateErrorsKey. The script notes execution is triggered when WSUS console is opened or a sync runs. 4) 4-verify.ps1 (post-exploitation verification/cleanup): Confirms execution by checking for the proof file locally or via \\WSUS\C$ admin share. It also connects to the WSUS Windows Internal Database (SUSDB) via the named pipe np:\\.\pipe\MICROSOFT##WID\tsql\query to count injected events (EventID=389) and optionally deletes them and removes artifacts (proof file and blob.txt). Overall purpose: provide purple-team exercise scripts that demonstrate an unauthenticated network-based RCE against WSUS by abusing anonymously accessible SOAP services to plant a malicious BinaryFormatter payload into WSUS’s database, which later deserializes during console load/synchronization.swoon69 · Disclosed Mar 9, 2026 · powershell · markdown · network (unauthenticated SOAP calls to WSUS endpoints leading to deserialization/RCE)OperationalWSUS-CVE-2025-59287-RCEThis repository contains a proof-of-concept exploit for CVE-2025-59287, a critical remote code execution vulnerability in Microsoft Windows Server Update Services (WSUS). The exploit is implemented in a single C# file (exploit.cs) and is designed to achieve unauthenticated remote code execution via insecure deserialization in the GetCookie endpoint. The exploit workflow involves generating a PowerShell reverse shell command, serializing it using ysoserial.net (TypeConfuseDelegate gadget), encrypting the payload with AES-128-CBC, and embedding it in a SOAP request sent to the target WSUS server. The attacker must provide the target URL, their own IP, and a listening port. If successful, the exploit grants a SYSTEM-level reverse shell to the attacker. The repository also includes a README with detailed usage instructions and a LICENSE file. The only code file is exploit.cs, which is the main entry point and contains all exploit logic. The exploit requires ysoserial.net.exe to be present in the same directory for payload generation.QurtiDev · Disclosed Nov 1, 2025 · csharp · networkPoCcve-2025-59287-exploit-pocThis repository is a comprehensive proof-of-concept (PoC) exploit for CVE-2025-59287, a critical unauthenticated remote code execution vulnerability in Microsoft Windows Server Update Services (WSUS). The exploit targets a deserialization flaw in the GetCookie() SOAP endpoint, which processes attacker-controlled, encrypted AuthorizationCookie data using .NET's BinaryFormatter without proper validation. The repository contains: - `wsus_exploit.py`: The main exploit script, written in Python, which sends a malicious SOAP request to the vulnerable WSUS endpoint. It can either encrypt a provided payload or use a pre-encrypted AuthorizationCookie. - `BinaryFormatterPayloadGenerator.cs`: A C# tool that generates a BinaryFormatter payload using the ObjectDataProvider gadget chain to execute arbitrary commands on the target system. The payload is output as a binary file and optionally as base64. - `encrypt_payload.py`: A Python script to encrypt the generated payload to match the WSUS AuthorizationCookie format. The script uses a placeholder key; real-world exploitation requires extracting the actual key from the target WSUS binaries. - `compile_payload_generator.bat`: A Windows batch script to compile the C# payload generator. - `requirements.txt`: Lists Python dependencies (requests, pycryptodome, urllib3). - `README.md`: Extensive documentation covering vulnerability details, exploitation workflow, key extraction instructions, detection guidance, and legal notice. The exploit workflow is: (1) generate a malicious .NET payload, (2) encrypt it as a WSUS AuthorizationCookie, and (3) send it to the vulnerable GetCookie() endpoint on the target WSUS server (typically on ports 8530/8531). If successful, this results in unauthenticated SYSTEM-level code execution. The repository is well-structured, with clear separation of payload generation, encryption, and exploitation logic. No hardcoded IPs or domains are present; the exploit is designed to be used against arbitrary WSUS targets specified by the user. The PoC is not weaponized (encryption key must be extracted by the user), but demonstrates a full attack chain for authorized testing and research.dexterm300 · Disclosed Nov 3, 2025 · python · csharp · networkPoCCVE-2025-59287This repository is a proof-of-concept exploit for CVE-2025-59287, a critical remote code execution vulnerability in Microsoft Windows Server Update Services (WSUS) due to unsafe deserialization of .NET objects. The repository contains four files: README.md (usage and background), encypt.py (prepares/encrypts payloads to mimic WSUS expected format), exp.py (main exploit script that crafts and sends SOAP requests to WSUS endpoints), and payload.txt (holds the base64-encoded .NET payload). The exploit works by sending a specially crafted SOAP request containing a malicious serialized object to the WSUS ReportingWebService endpoint, which, if vulnerable, will deserialize and execute the payload as SYSTEM. The code is written in Python and is structured for educational and demonstration purposes, with clear separation between payload preparation and exploitation logic. The endpoints targeted are typical WSUS SOAP web services, and the exploit is network-based, requiring only access to the WSUS server's HTTP(S) interface.th1n0 · Disclosed Nov 4, 2025 · python · networkPoCCVE-2025-59287-PoCThis repository provides a Python proof-of-concept (PoC) exploit for CVE-2023-35317 and CVE-2025-59287, which are deserialization vulnerabilities in Microsoft Windows Server Update Services (WSUS). The main exploit logic is contained in 'PoC.py', which orchestrates a multi-step SOAP-based attack against a target WSUS server. The exploit works by first obtaining a ServerId and authorization cookie from the WSUS server using crafted SOAP requests to specific endpoints. It then sends a malicious payload (either built-in or user-supplied, generated via ysoserial.net) to the server, exploiting the deserialization flaw to achieve remote code execution. The payload is typically a .NET gadget chain that can execute arbitrary commands on the server. The exploit can be triggered automatically or manually (e.g., when the WSUS console is opened), depending on the CVE targeted. The repository includes a README with detailed usage instructions and example commands. No hardcoded IPs or domains are present, but the exploit targets specific WSUS SOAP endpoints, making them fingerprintable. The code is a functional PoC and not weaponized for mass exploitation.M507 · Disclosed Nov 16, 2025 · python · networkPoCCVE-2025-59287This repository is a proof-of-concept exploit for CVE-2025-59287, a critical remote code execution vulnerability in Microsoft Windows Server Update Services (WSUS) due to unsafe .NET deserialization. The repository contains four files: a README.md with usage and vulnerability details, encypt.py (helper for preparing payloads), exp.py (the main exploit script), and payload.txt (for user-supplied payloads). The main exploit logic is in exp.py, which checks for the presence of WSUS SOAP endpoints on a target server, loads a .NET BinaryFormatter payload (either from payload.txt or a default benign payload), crafts a malicious SOAP request embedding the payload, and sends it to the WSUS server's /ApiRemoting30/WebService.asmx endpoint. If the server is vulnerable, the payload is deserialized and executed as SYSTEM. The exploit is network-based and requires only the target's URL and network access. The payload is customizable, allowing arbitrary code execution. The code is a proof-of-concept and does not include weaponized features such as automated callback verification or post-exploitation modules.vtntkmfyyftrem · Disclosed Jan 2, 2026 · python · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2025-59287 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Oct 24, 2025.
Is there a public exploit for CVE-2025-59287?
Yes. Mallory tracks 16 public exploits or proofs of concept for CVE-2025-59287, the earliest disclosed Oct 14, 2025.
Is there a patch for CVE-2025-59287?
Install the applicable Microsoft October 23, 2025 out-of-band security update or a later superseding update that includes the fix. Do not rely solely on the original October 2025 Patch Tuesday update.
What products are affected by CVE-2025-59287?
Microsoft Corporation Windows Server 2012, Microsoft Corporation Windows Server 2012 R2, Microsoft Corporation Windows Server 2016, Microsoft Corporation Windows Server 2019, Microsoft Corporation Windows Server 2022, and 3 more.
How severe is CVE-2025-59287?
CVE-2025-59287 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 100.0% (100th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

526 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+80 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence2Every report linking this CVE to a named adversary.
Associated malware13Malware families linked to this CVE, with evidence and IOCs.
Detection signatures5YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity115Community discussion across Reddit, Mastodon, and other social sources.