# Exploitation of WSUS RCE CVE-2025-59287 against a DMZ WSUS server at a global law firm, contained ~10 minutes after detection (Sygnia case study)

> Sygnia reports that on 2025-10-24 CVE-2025-59287 (unauthenticated deserialization RCE in Windows Server Update Services) was exploited against a WSUS server in a law firm's DMZ within hours of public PoC availability. Encoded PowerShell executed via WsusService.exe, followed by system enumeration and IIS web port modifications; a behavioral rule detected it and it was contained ~10 minutes later with no evidence of data loss, lateral movement, or persistence.

- **Published:** 2026-11-16T13:40:34Z
- **Last reviewed:** 2026-11-16T13:40:34Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6147
- **Card image:** https://intel.threadlinqs.com/og/threat/TL-2026-6147.png
- **ID:** TL-2026-6147
- **Severity:** CRITICAL (CVSS 9.8)
- **Category:** VULNERABILITY
- **Status:** PATCHED
- **Detections:** 9 (1 shown free below) · **IOCs:** 16 (3 shown free below)
- **CVEs:** CVE-2025-59287

## Description

CVE-2025-59287 is a CVSS 9.8 (CWE-502) unsafe-deserialization flaw in Windows Server Update Services. Per Unit 42, a crafted request to the GetCookie() endpoint causes an AuthorizationCookie object to be deserialized with BinaryFormatter, and a second path via the ReportingWebService triggers unsafe deserialization through SoapFormatter. Successful exploitation yields unauthenticated remote code execution as SYSTEM. Only servers with the WSUS Server Role enabled (not default) are affected; the service listens on TCP 8530 (HTTP) and 8531 (HTTPS). The initial October 14, 2025 Patch Tuesday fix was incomplete; Microsoft shipped an out-of-band update on October 23, 2025 (KB5070883 for Server 2019, build 17763.7922). HawkTrace published a PoC around October 22, 2025 (secondary sources differ on the exact date; one says October 18). Eye Security observed that real-world exploitation used a ysoserial.net-built payload (likely ActivitySurrogateSelector gadget) embedding a .NET binary that runs cmd.exe /c with the value of an HTTP header named 'aaaa' and returns output in the HTTP response, which is more capable than the public PoC that only launches calc.

Sygnia case study (client: a top global law firm): on October 24, 2025 the vulnerability was publicly disclosed around 12:00 per the case study, and at about 18:00 a production WSUS server in the client's DMZ triggered the behavioral analytics alert 'Sequence Of Encoded Commands'. The activity was multiple encoded PowerShell commands run through WsusService.exe, system enumeration, IIS web port modifications, and activity suggesting data exfiltration staging through altered network paths. The analyst correlated the alert with the public PoC that had surfaced hours earlier. After a short client validation delay due to production sensitivity, containment was completed about 10 minutes after detection (~18:10). Scope escalated to incident response: forensic review for persistence or backdoors, validation of no exfiltration, hardening, and patch validation. No data loss, lateral movement, or persistence was detected; WSUS infrastructure was remediated and patched and detection tuning for CVE-based exploitation was improved. The Sygnia page publishes no IPs, hashes, commands, or ATT&CK IDs and no actor attribution.

Broader campaign context from other vendors: Huntress first saw exploitation at ~2025-10-23 23:34 UTC across four customers, through proxy networks, with process chains wsusservice.exe/w3wp.exe -> cmd.exe -> cmd.exe -> powershell.exe running a base64 (-ec) command that enumerated the domain (whoami; net user /domain; ipconfig /all) and exfiltrated output to a webhook.site endpoint via Invoke-WebRequest with curl.exe fallback. Eye Security traced an exploit source to VPS 207.180.254.242. CISA added the CVE to KEV on 2025-10-24 (due 2025-11-14). Exposure estimates vary: ~8,000 hosts on 8530/8531 (Eye Security, unverified vulnerable), ~5,500 (Unit 42 Cortex Xpanse), ~2,500 (Eye Security statement as relayed by secondary sources).

## MITRE ATT&CK

- T1190 Exploit Public-Facing Application
- T1059.001 Command and Scripting Interpreter: PowerShell
- T1059.003 Command and Scripting Interpreter: Windows Command Shell
- T1027.010 Obfuscated Files or Information: Command Obfuscation
- T1033 System Owner/User Discovery
- T1087.002 Account Discovery: Domain Account
- T1071.001 Application Layer Protocol: Web Protocols
- T1090 Proxy
- T1567 Exfiltration Over Web Service

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**CVE-2025-59287 WSUS Service or WsusPool w3wp Spawning Shell / Recon Child Process (Exploitation)** (`TL-2026-6147-SPL-001`)

Detects wsusservice.exe, or the WSUS IIS application pool worker (w3wp.exe -ap WsusPool), spawning cmd.exe, powershell.exe, whoami.exe, curl.exe or net/ipconfig. The CVE-2025-59287 BinaryFormatter/SoapFormatter deserialization RCE runs attacker commands as SYSTEM inside these processes (Sygnia: encoded PowerShell via WsusService.exe; Huntress/Eye Security: wsusservice.exe/w3wp.exe -> cmd.exe -> powershell.exe, w3wp.exe -> whoami.exe). WSUS has no legitimate reason to launch shells or recon tools.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1190, T1059.001, T1059.003, T1033, T1087.002
- **Data sources:** sysmon (Event ID 1), microsoft_defender_for_endpoint DeviceProcessEvents, windows_security 4688
- **Severity:** critical
- **Confidence:** high

### Splunk SPL

```spl
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 (ParentImage="*\\wsusservice.exe" OR (ParentImage="*\\w3wp.exe" AND ParentCommandLine="*wsuspool*")) (Image="*\\cmd.exe" OR Image="*\\powershell.exe" OR Image="*\\pwsh.exe" OR Image="*\\whoami.exe" OR Image="*\\curl.exe" OR Image="*\\net.exe" OR Image="*\\net1.exe" OR Image="*\\ipconfig.exe")
| eval encoded_ps=if(match(CommandLine,"(?i) -(e|ec|enc|encodedcommand) +[A-Za-z0-9+/=]{20,}"),"yes","no")
| stats count min(_time) as first_seen max(_time) as last_seen values(Image) as child_images values(CommandLine) as command_lines values(encoded_ps) as encoded_ps by host ParentImage ParentCommandLine User
| convert ctime(first_seen) ctime(last_seen)
```

### Microsoft KQL

```kql
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName in~ ("cmd.exe","powershell.exe","pwsh.exe","whoami.exe","curl.exe","net.exe","net1.exe","ipconfig.exe")
| where InitiatingProcessFileName =~ "wsusservice.exe" or (InitiatingProcessFileName =~ "w3wp.exe" and InitiatingProcessCommandLine has "wsuspool")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessParentFileName, SHA256
```

### Sigma

```yaml
title: CVE-2025-59287 WSUS Service or WsusPool Worker Spawning Shell or Recon Process
id: 6b1f0a52-3c47-4d9e-9a1e-5f2a7c8d1001
status: experimental
description: Detects wsusservice.exe or the WSUS IIS app pool worker (w3wp.exe WsusPool) spawning cmd, PowerShell, whoami, curl, net or ipconfig, as seen in exploitation of the WSUS deserialization RCE CVE-2025-59287.
references:
    - https://www.sygnia.co/case-study/case-study-rapid-containment-of-exploitation-attempt/
    - https://www.huntress.com/blog/exploitation-of-windows-server-update-services-remote-code-execution-vulnerability
    - https://labs.eye.security/wsus-deserialization-exploit-in-the-wild-cve-2025-59287/
    - https://nvd.nist.gov/vuln/detail/CVE-2025-59287
author: Threadlinqs Team
date: 2026-11-16
tags:
    - attack.initial-access
    - attack.t1190
    - attack.execution
    - attack.t1059.001
    - attack.t1059.003
    - attack.discovery
    - attack.t1033
    - attack.t1087.002
    - cve.2025-59287
logsource:
    category: process_creation
    product: windows
detection:
    selection_wsus:
        ParentImage|endswith: '\wsusservice.exe'
    selection_iis:
        ParentImage|endswith: '\w3wp.exe'
        ParentCommandLine|contains: 'WsusPool'
    selection_child:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
            - '\pwsh.exe'
            - '\whoami.exe'
            - '\curl.exe'
            - '\net.exe'
            - '\net1.exe'
            - '\ipconfig.exe'
    condition: (selection_wsus or selection_iis) and selection_child
falsepositives:
    - Administrator troubleshooting that launches a shell from a WSUS maintenance wrapper
    - Third-party patch tooling hosted in the WsusPool app pool
level: critical

```

**Known false positives:**

- Administrator-run maintenance scripts launched by a WSUS scheduled task wrapper
- Vulnerability scanners or EDR response actions that spawn cmd.exe under wsusservice.exe during testing

**Tuning notes:** Scope to hosts running the WSUS Server Role (lookup of WSUS hostnames). Alert on any hit; this parent/child pairing has near-zero benign baseline. Ensure Sysmon logs ParentCommandLine so the WsusPool filter works, and exclude sanctioned maintenance scripts by CommandLine.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- CVE-2025-59287 WSUS Exploit Request Sequence from External Client (IIS Log, Ports 8530/8531) (locked: unlock with TL Creds)
- CVE-2025-59287 Encoded PowerShell Following WSUS Process Child Spawn (Sequence of Encoded Commands) (locked: unlock with TL Creds)
- CVE-2025-59287 Server Process Network Activity to [indicator] or Exploit VPS (MDE) (locked: unlock with TL Creds)
- CVE-2025-59287 WSUS SoftwareDistribution.log Deserialization Exploit Artifacts (locked: unlock with TL Creds)
- CVE-2025-59287 PowerShell Script Block Exfiltrating Enumeration Output to [indicator] (locked: unlock with TL Creds)
- CVE-2025-59287 curl.exe -k --data-binary / [indicator] Command Line Exfiltration (locked: unlock with TL Creds)
- CVE-2025-59287 Post-Exploitation Domain and Network Enumeration on WSUS Host (whoami / net user /domain / ipconfig /all) (locked: unlock with TL Creds)
- CVE-2025-59287 Exfiltration DNS/Connection to [indicator] or Exploit VPS [indicator] (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (3 of 16)

Defanged, TLP:CLEAR.

- IP address: `207.180.254[.]242`
- Domain: `webhook[.]site`
- File hash: `ac7351b617f85863905ba8a30e46a112a9083f4d388fd708ccfe6ed33b5cf91d`

Full set of 16 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [Sygnia Case Study: Rapid Containment of Exploitation Attempt](https://www.sygnia.co/case-study/case-study-rapid-containment-of-exploitation-attempt/)
- [NVD - CVE-2025-59287](https://nvd.nist.gov/vuln/detail/CVE-2025-59287)
- [Microsoft MSRC Update Guide - CVE-2025-59287](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59287)
- [CISA Known Exploited Vulnerabilities Catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog)
- [Huntress: Exploitation of WSUS RCE Vulnerability (CVE-2025-59287)](https://www.huntress.com/blog/exploitation-of-windows-server-update-services-remote-code-execution-vulnerability)
- [Eye Security: WSUS deserialization exploit in the wild (CVE-2025-59287)](https://labs.eye.security/wsus-deserialization-exploit-in-the-wild-cve-2025-59287/)
- [Unit 42: Microsoft WSUS RCE CVE-2025-59287](https://unit42.paloaltonetworks.com/microsoft-cve-2025-59287/)
- [Triskele Labs: CVE-2025-59287 Vulnerability in WSUS Servers](https://www.triskelelabs.com/blog/cve-2025-59287-vulnerability-in-wsus-servers)
- [Bitdefender Technical Advisory: Critical Unauthenticated RCE in WSUS (CVE-2025-59287)](https://www.bitdefender.com/en-us/blog/businessinsights/bitdefender-advisory-critical-unauthenticated-rce-windows-server-update-services-cve-2025-59287)
- [Picus Security: CVE-2025-59287 Explained](https://www.picussecurity.com/resource/blog/cve-2025-59287-explained-wsus-unauthenticated-rce-vulnerability)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6147
