Microsoft Patches 3 Zero-Days Under Active Attack in Massive October Update

Microsoft's October 2025 Patch Tuesday Addresses 175 Vulnerabilities, Including Three Actively Exploited Zero-Days

CRITICAL
October 6, 2025
5m read
Patch ManagementVulnerabilityCyberattack

Related Entities

Organizations

Products & Tech

WindowsWindows Server Update Services (WSUS)Microsoft OfficeAzureIGEL OS

CVE Identifiers

CVE-2025-59230
HIGH
CVSS:7.8
CVE-2025-24990
HIGH
CVSS:7.8
CVE-2025-47827
MEDIUM
CVSS:4.6
CVE-2025-59287
CRITICAL
CVSS:9.8

Full Report

Executive Summary

In one of the most significant security updates of the year, Microsoft has released its October 2025 Patch Tuesday, remediating 175 vulnerabilities across Windows, Office, Azure, and other products. The most urgent fixes address three zero-day vulnerabilities that are being actively exploited by threat actors. These flaws, which allow for privilege escalation and Secure Boot bypass, have been added to the CISA Known Exploited Vulnerabilities (KEV) catalog, mandating immediate action from federal agencies and signaling a widespread threat to all organizations. The update also includes a patch for a critical-rated (CVSS 9.8) Remote Code Execution (RCE) vulnerability in Windows Server Update Services (WSUS) that could be leveraged for devastating supply-chain attacks.


Vulnerability Details

The October 2025 update is notable for the severity and active exploitation of several key vulnerabilities:

Actively Exploited Zero-Days

  1. CVE-2025-59230 - Windows Remote Access Connection Manager (RasMan) Privilege Escalation: This vulnerability, with a CVSS score of 7.8, allows a local attacker to gain SYSTEM-level privileges due to an improper access control weakness. Its exploitation in the wild marks a novel attack vector against the RasMan component.

  2. CVE-2025-24990 - Agere Modem Driver Privilege Escalation: Also rated CVSS 7.8, this flaw exists in the legacy ltmdm64.sys driver. Attackers can exploit it to elevate privileges to the local administrator level. Microsoft's patch takes the unusual step of completely removing the vulnerable driver, which may impact legacy hardware.

  3. CVE-2025-47827 - Secure Boot Bypass: This lower-severity (CVSS 4.6) but highly significant flaw affects Linux-based IGEL OS. However, because Microsoft's UEFI Certificate Authority trusted the vulnerable IGEL component, it allows attackers to bypass Secure Boot protections on Windows devices, undermining a fundamental security layer.

Other Critical Vulnerabilities

  • CVE-2025-59287 - Windows Server Update Services (WSUS) RCE: A critical vulnerability with a CVSS score of 9.8. This flaw could allow an attacker to execute arbitrary code on WSUS servers, creating a powerful vector for supply-chain attacks by pushing malicious updates to downstream clients.
  • CVE-2025-59291 & CVE-2025-59292 - Azure Flaws: These vulnerabilities impact Azure Container Instances and Compute Gallery, highlighting ongoing risks in cloud infrastructure environments.

Affected Systems

The vulnerabilities impact a wide range of Microsoft products, including but not limited to:

  • All supported versions of Windows and Windows Server
  • Windows Server Update Services (WSUS)
  • Microsoft Office & Microsoft Excel
  • Microsoft Azure Container Instances
  • Microsoft Azure Compute Gallery
  • Devices using Secure Boot that trust the affected IGEL component

Exploitation Status

CVE-2025-59230, CVE-2025-24990, and CVE-2025-47827 are confirmed to be actively exploited in the wild. All three have been added to the CISA KEV catalog, with a remediation deadline of November 4, 2025, for U.S. federal agencies. The active exploitation significantly increases the risk profile for all organizations, as exploit code is available to a wider range of threat actors.

Impact Assessment

The business impact of these vulnerabilities is severe. Successful exploitation of the privilege escalation flaws (CVE-2025-59230, CVE-2025-24990) can allow an attacker with an initial low-privilege foothold to take complete control of a system, disable security software, and move laterally across the network. The Secure Boot bypass (CVE-2025-47827) undermines trust at the hardware level, enabling persistent bootkits that are difficult to detect and remove. The WSUS RCE (CVE-2025-59287) represents a catastrophic supply-chain risk, where a single compromised server could be used to distribute malware to thousands of endpoints within an organization.

Cyber Observables for Detection

Security teams can hunt for signs of vulnerable systems or exploitation attempts:

Type Value Description
file_name ltmdm64.sys Presence of the legacy Agere Modem driver on systems indicates vulnerability to CVE-2025-24990 prior to patching.
log_source Windows Security Event Log Monitor for anomalous process creation or service modifications related to the Remote Access Connection Manager (RasMan) service.
command_line_pattern powershell -enc Often used by attackers after successful privilege escalation to download next-stage payloads.
event_id 4688 Monitor for suspicious child processes spawned by services that should not normally execute commands, such as svchost.exe hosting RasMan.

Detection & Response

  • Vulnerability Scanning: Use authenticated vulnerability scanners to identify systems missing the October 2025 security updates. Prioritize systems based on CISA KEV catalog entries.
  • Endpoint Detection and Response (EDR): Deploy EDR solutions to monitor for post-exploitation behavior associated with privilege escalation. Look for processes gaining SYSTEM integrity levels or suspicious child processes being spawned by system services.
  • Log Analysis: Ingest Windows Event Logs into a SIEM. Create detection rules for unusual activity related to the RasMan service and monitor for logs indicating a Secure Boot integrity failure.
  • D3FEND Techniques: Employ D3-PA: Process Analysis to baseline normal process behavior and detect anomalies indicative of exploitation. Use D3-SFA: System File Analysis to verify the integrity of critical system files and drivers.

Mitigation

  • Immediate Patching: The primary mitigation is to apply the October 2025 security updates from Microsoft immediately. Prioritize patching based on risk: first, internet-facing systems, then critical servers (Domain Controllers, WSUS servers), and finally all workstations.
  • Principle of Least Privilege: Enforce the principle of least privilege for all user accounts. This can limit the impact of a successful privilege escalation attack, as the initial foothold will have minimal access.
  • Application Control: Implement application control policies, such as Windows Defender Application Control (WDAC), to restrict the execution of unauthorized code, which can prevent attackers from running payloads after exploiting an EoP flaw.
  • WSUS Hardening: Isolate the WSUS server network from general user networks. Strictly control access to the WSUS administrative console and ensure it is patched as a top priority.
  • D3FEND Countermeasures: Implement hardening measures such as D3-PH: Platform Hardening and ensure D3-SU: Software Update processes are robust and timely.

Timeline of Events

1
October 5, 2025
Microsoft releases its October 2025 Patch Tuesday security updates.
2
October 5, 2025
CISA adds CVE-2025-59230, CVE-2025-24990, and CVE-2025-47827 to its Known Exploited Vulnerabilities (KEV) catalog.
3
October 6, 2025
This article was published

MITRE ATT&CK Mitigations

The most critical mitigation is to apply the security patches provided by Microsoft to eliminate the vulnerabilities.

Mapped D3FEND Techniques:

Restrict privileges for user accounts and services to limit the impact of a successful privilege escalation attack.

Mapped D3FEND Techniques:

Ensure Secure Boot is properly configured and monitored to detect and prevent bypass attempts like CVE-2025-47827.

Mapped D3FEND Techniques:

Audit

M1047enterprise

Implement comprehensive logging and auditing to detect post-exploitation activities and anomalous system behavior.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

Immediately deploy Microsoft's October 2025 security updates to all affected systems. Utilize a centralized patch management solution like WSUS (once patched itself) or Microsoft Endpoint Configuration Manager to automate deployment. Prioritize systems based on risk: internet-facing servers first, followed by critical infrastructure like Domain Controllers and WSUS servers, and then the general workstation fleet. Establish a verification process to confirm that patches have been successfully applied across the environment. For the WSUS RCE (CVE-2025-59287), the WSUS server itself must be patched before it can be trusted to distribute other updates. Consider using out-of-band patching methods for WSUS if necessary. Given the active exploitation, these updates should be treated as an emergency change and deployed outside of normal patching cycles.

Leverage an EDR solution to perform deep process analysis on endpoints, specifically monitoring for signs of privilege escalation. For CVE-2025-59230, this involves baselining the normal behavior of processes running under the RasMan service context (svchost.exe) and alerting on any anomalous child processes, such as the spawning of cmd.exe or powershell.exe. For CVE-2025-24990, monitor for any process that attempts to load or interact with the ltmdm64.sys driver. Create detection rules that trigger when a process unexpectedly gains SYSTEM-level integrity. This proactive monitoring can detect exploitation of these zero-days even before patches are fully deployed, enabling rapid incident response.

Sources & References

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

Patch TuesdayZero-DayPrivilege EscalationRCESecure BootWindowsCISA KEV

📢 Share This Article

Help others stay informed about cybersecurity threats

Continue Reading