CVE-2026-21236
vulnerability analysis and mitigation

Overview

CVE-2026-21236 is a heap-based buffer overflow vulnerability in the Windows Ancillary Function Driver (AFD) for WinSock that allows a low-privileged local attacker to escalate privileges without user interaction. It was disclosed and patched on February 10, 2026, as part of Microsoft's February 2026 Patch Tuesday security update. Affected products span a wide range of Windows versions including Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1), Windows Server 2012/R2, 2016, 2019, 2022 (including 23H2), and 2025. The vulnerability carries a CVSS v3.1 base score of 7.8 (High) (Microsoft MSRC, Feedly).

Technical details

The vulnerability is classified as CWE-122 (Heap-based Buffer Overflow) and CWE-787 (Out-of-bounds Write), rooted in improper memory management within the Windows Ancillary Function Driver (afd.sys) for WinSock. An attacker with low-privilege local access can trigger the overflow to corrupt heap memory, potentially redirecting execution flow to achieve privilege escalation. The attack vector is local, requires low privileges, and no user interaction, making it straightforward to exploit once an attacker has a foothold on the system. NCC Group published a vulnerability analysis of this CVE, providing additional technical depth (NCC Group, Microsoft MSRC).

Impact

Successful exploitation allows a low-privileged attacker to elevate to SYSTEM-level privileges on the affected Windows host, resulting in high impact to confidentiality, integrity, and availability. An attacker who gains SYSTEM privileges can install malware, access all data on the system, create new accounts, disable security controls, and potentially pivot laterally within a network. The broad scope of affected Windows versions — spanning client and server editions from Windows 10 1607 through Windows Server 2025 — significantly widens the potential attack surface (Microsoft MSRC, Feedly).

Exploitation steps

  1. Gain Initial Access: Obtain a low-privileged user account on a vulnerable Windows system (e.g., via phishing, credential theft, or exploitation of another vulnerability).
  2. Identify Target Driver: Confirm the target system runs a vulnerable version of afd.sys (Windows Ancillary Function Driver for WinSock) by checking the OS build number against the patched versions.
  3. Craft Malicious Input: Develop or obtain a payload that triggers the heap-based buffer overflow in the AFD driver by sending specially crafted WinSock-related system calls or IOCTL requests that exceed expected buffer boundaries.
  4. Trigger the Overflow: Execute the crafted payload locally, causing out-of-bounds writes to heap memory within the kernel driver, corrupting adjacent memory structures.
  5. Achieve Privilege Escalation: Leverage the corrupted memory to redirect kernel execution flow, overwrite security tokens, or manipulate process privileges to escalate from a low-privileged user to SYSTEM.
  6. Post-Exploitation: With SYSTEM privileges, deploy persistence mechanisms, exfiltrate data, disable endpoint defenses, or move laterally within the network (NCC Group, Microsoft MSRC).

Indicators of compromise

  • Process: Unexpected processes spawned with SYSTEM-level privileges from a standard user context; unusual child processes of svchost.exe or other system processes.
  • Logs: Windows Security Event Log entries showing privilege escalation (Event ID 4672 – Special privileges assigned to new logon) from low-privileged accounts; kernel crash dumps (BSOD) referencing afd.sys during exploitation attempts.
  • File System: Presence of new or modified files in system directories (e.g., %SystemRoot%\System32) created by non-administrative accounts; unexpected scheduled tasks or services created post-compromise.
  • Network: Unusual outbound connections from SYSTEM-level processes to external IPs, potentially indicating post-exploitation C2 activity.
  • Registry: New or modified registry run keys or services created by accounts that should not have such permissions (NCC Group).

Mitigation and workarounds

Microsoft released patches on February 10, 2026, addressing all affected Windows versions. Administrators should apply the following updates or later: Windows 10 1607 → 10.0.14393.8868; Windows 10 1809/Server 2019 → 10.0.17763.8389; Windows 10 21H2 → 10.0.19044.6937; Windows 10 22H2 → 10.0.19045.6937; Windows 11 23H2 → 10.0.22631.6649; Windows 11 24H2/Server 2025 → 10.0.26100.7781; Windows 11 25H2 → 10.0.26200.7781; Windows Server 2022 → 10.0.20348.4711; Windows Server 2022 23H2 → 10.0.25398.2149. As interim measures, restrict local interactive and remote desktop access to trusted users only, enforce the principle of least privilege, and monitor for suspicious privilege escalation activity targeting WinSock-related components (Microsoft MSRC).

Community reactions

The vulnerability was covered as part of broader February 2026 Patch Tuesday reporting by BleepingComputer, Rapid7, Sophos, and SANS ISC, all of which highlighted the month's six actively exploited zero-days alongside this EoP flaw (BleepingComputer, Rapid7, Sophos). NCC Group published a dedicated vulnerability analysis of CVE-2026-21236, indicating researcher interest in the technical details of the AFD driver flaw (NCC Group). Security community discussion on social platforms (Mastodon, X/Twitter) was moderate, consistent with a non-zero-day EoP vulnerability patched in a large monthly update.

Additional resources


SourceThis report was generated using AI

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management