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.
The February 2026 Patch Tuesday addresses a total of 58 flaws, with a heavy focus on privilege escalation. The breakdown of vulnerability types includes:
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 |
The zero-days present clear and distinct attack paths for threat actors:
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.
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.
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.
T1204.002 - Malicious File: Exploitation of Word and MSHTML flaws relies on user interaction with a malicious file.T1548.002 - Bypass User Account Control: The security feature bypass flaws are a form of UAC bypass, tricking the user and OS into running untrusted code.T1068 - Exploitation for Privilege Escalation: The DWM and RDS flaws are used to escalate from user to SYSTEM privileges.T1485 - Data Destruction: While CVE-2026-21525 is a DoS, it can be used as part of a destructive attack to hinder recovery efforts.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.
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 |
mshta.exe, rundll32.exe, and Office applications spawning unusual child processes (e.g., powershell.exe, cmd.exe).svchost.exe (hosting DWM or RDS) or winword.exe.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.CVE-2026-21514.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.
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.

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.
Help others stay informed about cybersecurity threats