Microsoft Scrambles to Fix Six Actively Exploited Zero-Days in February 2026 Patch Tuesday

Microsoft's February 2026 Patch Tuesday Addresses 58 Flaws, Including Six Actively Exploited Zero-Days

CRITICAL
February 11, 2026
February 14, 2026
7m read
Patch ManagementVulnerabilityCyberattack

Related Entities(initial)

Organizations

CrowdStrikeMalwarebytesMicrosoft

Products & Tech

MSHTMLMicrosoft OfficeMicrosoft WindowsMicrosoft WordWindows Desktop Window ManagerWindows Remote Access Connection ManagerWindows Remote Desktop ServicesWindows Shell

CVE Identifiers

CVE-2026-21510
HIGH
CVSS:8.8
CVE-2026-21513
HIGH
CVSS:8.8
CVE-2026-21514
MEDIUM
CVSS:5.5
CVE-2026-21519
HIGH
CVSS:7.8
CVE-2026-21525
MEDIUM
CVSS:6.2
CVE-2026-21533
HIGH
CVSS:7.8

Full Report(when first published)

Executive Summary

On February 11, 2026, Microsoft released its monthly security update, addressing 58 vulnerabilities. The release is dominated by the inclusion of patches for six zero-day vulnerabilities that were confirmed to be actively exploited in the wild. These critical flaws span major components including Windows Shell, MSHTML, Microsoft Word, Desktop Window Manager, and Remote Desktop Services. The vulnerabilities primarily enable security feature bypasses and privilege escalation, allowing attackers to execute code silently or gain full SYSTEM-level control of compromised machines. Given the active exploitation, CISA is expected to add these to its Known Exploited Vulnerabilities (KEV) catalog. All organizations are urged to apply these updates with the highest priority to mitigate the immediate and significant risk of compromise.


Vulnerabilities Addressed

The February 2026 Patch Tuesday addresses a total of 58 flaws, with a heavy focus on privilege escalation. The breakdown of vulnerability types includes:

  • 25 Elevation of Privilege (EoP) Vulnerabilities
  • 12 Remote Code Execution (RCE) Vulnerabilities
  • 5 Security Feature Bypass Vulnerabilities
  • 5 Denial of Service (DoS) Vulnerabilities
  • 11 Information Disclosure Vulnerabilities

The most critical vulnerabilities are the six zero-days actively exploited in the wild:

CVE ID Description CVSS Score Type KEV Status
CVE-2026-21510 Windows Shell Security Feature Bypass 8.8 Security Feature Bypass Yes
CVE-2026-21513 MSHTML (Trident) Security Feature Bypass 8.8 Security Feature Bypass Yes
CVE-2026-21519 Desktop Window Manager (DWM) Elevation of Privilege 7.8 Elevation of Privilege Yes
CVE-2026-21533 Windows Remote Desktop Services Elevation of Privilege 7.8 Elevation of Privilege Yes
CVE-2026-21514 Microsoft Word Security Feature Bypass 5.5 Security Feature Bypass Yes
CVE-2026-21525 Remote Access Connection Manager (RasMan) Denial of Service 6.2 Denial of Service Yes

Technical Analysis

The zero-days present clear and distinct attack paths for threat actors:

  1. Security Feature Bypass (CVE-2026-21510, CVE-2026-21513, CVE-2026-21514): These vulnerabilities are prime for initial access and payload delivery. Attackers can craft malicious links, shortcuts (.lnk), or documents that, when opened by a user, bypass critical OS security warnings like SmartScreen or Protected View. This allows for the seamless execution of malware. This technique aligns with T1204.002 - Malicious File and T1559.002 - Dynamic Data Exchange, where trusted application features are abused.

  2. Elevation of Privilege (CVE-2026-21519, CVE-2026-21533): Once an attacker has a low-privilege foothold on a system (e.g., from a phishing attack), these vulnerabilities provide a direct path to SYSTEM-level control. The DWM and RDS flaws are local exploits, meaning the attacker must already have code execution capabilities on the target. This is a classic example of T1068 - Exploitation for Privilege Escalation. Gaining SYSTEM privileges allows attackers to disable security software, install rootkits, and move laterally across the network.

  3. Denial of Service (CVE-2026-21525): While less severe, the RasMan DoS flaw can be used for disruption, particularly in environments reliant on VPNs for remote access. An attacker could use this to disrupt security operations or force users onto less secure networks.

MITRE ATT&CK Mapping


Impact Assessment

The immediate impact is high for all organizations running unpatched Windows systems. The security feature bypass vulnerabilities lower the bar for successful phishing campaigns, as they remove key visual warnings that trained users rely on. The privilege escalation flaws are a critical component in post-exploitation attack chains, enabling ransomware deployment, data exfiltration, and persistent access. Industries that are common targets for cybercrime, such as healthcare, finance, and critical infrastructure, are at heightened risk. The combination of a bypass and an EoP flaw creates a potent attack chain, allowing an attacker to go from a single click to full domain compromise.

Cyber Observables for Detection

Security teams should hunt for signs of pre-patch exploitation:

Type Value Description Context
command_line_pattern mshta.exe http://<suspicious_domain>/file.html Execution of remote HTML content via mshta.exe, potentially related to CVE-2026-21513 exploitation. Process creation logs (Event ID 4688)
file_name *.lnk Suspicious .lnk files in email attachments or downloads, potentially crafted for CVE-2026-21510. EDR/Antivirus logs, file system monitoring
process_name dwm.exe Monitor for anomalous child processes or crashes of the Desktop Window Manager (dwm.exe). Windows System Event Logs, EDR telemetry
log_source Microsoft-Windows-TerminalServices-LocalSessionManager/Operational Look for unexpected or rapid successful logons via RDS, which could indicate exploitation of CVE-2026-21533. Windows Event Logs on terminal servers
event_id 4624 with Logon Type 10 Correlate with unusual source IPs or accounts for signs of RDS abuse. Security Event Log

Detection & Response

  • Prioritize alerts related to mshta.exe, rundll32.exe, and Office applications spawning unusual child processes (e.g., powershell.exe, cmd.exe).
  • Implement enhanced monitoring for endpoint security logs. Look for evidence of security warnings being programmatically dismissed or bypassed.
  • Hunt for exploitation of privilege escalation: Query EDR data for processes that start with low or medium integrity and are later seen running as SYSTEM, especially if the parent process is svchost.exe (hosting DWM or RDS) or winword.exe.
  • D3FEND Techniques: Employ D3-PA: Process Analysis to baseline normal process behavior and detect anomalies. Use D3-UBA: User Behavior Analysis to spot users executing files from untrusted locations.

Mitigation

  1. Patch Immediately: The top priority is to deploy the February 2026 security updates to all affected systems. Prioritize internet-facing servers, workstations used by privileged users, and critical infrastructure. Use a risk-based approach, but aim for full deployment within 72 hours due to active exploitation.
  2. Enable Attack Surface Reduction (ASR) Rules: Configure ASR rules to block Office applications from creating child processes, executing malicious content, or making Win32 API calls. This provides a strong compensating control against CVE-2026-21514.
  3. Review User Privileges: Enforce the principle of least privilege. Standard users should not have administrative rights. This won't prevent exploitation of the EoP flaws but will contain the blast radius of other attacks.
  4. Harden Remote Desktop Services: If RDS is not required, disable it. If it is, restrict access to authorized users via a bastion host or VPN and enforce Multi-Factor Authentication (MFA).

CRITICAL WARNING: Due to the active in-the-wild exploitation of these vulnerabilities, organizations must assume they are being actively targeted. Patching should be treated as an emergency action. Post-patching, a threat hunt for signs of compromise is strongly recommended.

Timeline of Events

1
February 10, 2026
Microsoft releases its February 2026 Patch Tuesday security updates.
2
February 11, 2026
This article was published

Article Updates

February 14, 2026

Microsoft initiates phased rollout of updated Secure Boot certificates to replace legacy ones expiring in June 2026, enhancing system integrity.

In addition to the February 2026 Patch Tuesday fixes, Microsoft has commenced a phased rollout of new Secure Boot certificates. These certificates are crucial for maintaining system integrity and are replacing older ones set to expire in June 2026. This proactive measure aims to prevent future boot-up issues and protect against bootkit and rootkit malware, ensuring the continued security of Windows systems. This update is a significant infrastructure change alongside the vulnerability patches.

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 TuesdayPrivilege EscalationRCESecurity Feature BypassVulnerabilityWindowsZero-Day

📢 Share This Article

Help others stay informed about cybersecurity threats