Microsoft October 2025 patches, three CVEs actively exploited
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Microsoft released October 2025 security updates; CVE-2025-24990, CVE-2025-47827, CVE-2025-59230 are actively exploited; CVE-2025-59287 affects Windows Server with high impact.
Japan's IPA (Information-technology Promotion Agency) published a security alert on October 15, 2025, regarding Microsoft's monthly security update release. The advisory identifies three vulnerabilities already under active exploitation in the wild: CVE-2025-24990, CVE-2025-47827, and CVE-2025-59230. These flaws carry a range of impacts from denial of service through application crashes to remote code execution enabling attacker control of affected systems. On October 27, 2025, Microsoft released an out-of-band security update to comprehensively address CVE-2025-59287 affecting Windows Server, which carries significant impact if exploited. IPA urges immediate deployment of all patches through Windows Update, which typically delivers and installs security updates automatically. Organizations managing patch deployments should prioritize these updates given the confirmed active exploitation.
Mentioned in this report
Detection guidance
IIS Worker Process Spawning Command Shell or Scripting Host
w3wp.exe spawning cmd, PowerShell or script interpreters, a common post-exploitation pattern after RCE against a public-facing Windows web application. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: IIS Worker Process Spawning Command Shell or Scripting Host
description: Detects the IIS worker process w3wp.exe spawning a shell or scripting
host or living-off-the-land binary. This is a generic behavioural indicator of successful
exploitation of a public-facing Windows web application (RCE or webshell). The patch
advisory itself gives no process-level detail.
tags:
- attack.initial-access
- attack.t1190
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: \w3wp.exe
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \certutil.exe
- \bitsadmin.exe
condition: selection
falsepositives:
- Web applications that legitimately shell out to cmd.exe or PowerShell for administrative
tasks
- Legacy deployment or health-check scripts launched from an IIS application
level: medium
id: 36a8c0b0-d40a-555e-8291-1f4cc933eb4c
status: experimental
author: Vorant
references:
- https://www.ipa.go.jp/security/security-alert/2025/1015-ms.html
WSUS Service or WSUS App Pool Spawning Shell
WSUS service process or the IIS WsusPool worker spawning command interpreters, consistent with RCE exploitation of Windows Server update services. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: WSUS Service or WSUS App Pool Spawning Shell
description: Detects WSUS components (wsusservice.exe or the w3wp.exe WsusPool application
pool) spawning cmd, PowerShell or similar interpreters. WSUS has no routine need
to launch interactive shells, so this indicates likely remote code execution against
Windows Server, such as the out-of-band CVE-2025-59287 fix scenario.
tags:
- attack.initial-access
- attack.t1190
logsource:
category: process_creation
product: windows
detection:
selection_parent:
- ParentImage|endswith: \wsusservice.exe
- ParentImage|endswith: \w3wp.exe
ParentCommandLine|contains: WsusPool
selection_child:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \certutil.exe
- \bitsadmin.exe
condition: selection_parent and selection_child
falsepositives:
- Custom WSUS maintenance or cleanup scripts triggered by the WSUS service account
level: high
id: 447d22bc-1123-5f7a-8d51-dffebeddc7f9
status: experimental
author: Vorant
references:
- https://www.ipa.go.jp/security/security-alert/2025/1015-ms.html
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.ipa.go.jp/security/security-alert/2025/1015-ms.html
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,853 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs