Skip to content
Reachability Analysis

CVE-2026-68820: Microsoft Windows AFD for WinSock, is it exploitable where you run it

Code called: yesReached: openControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

CVE-2026-68820 is a use-after-free (CWE-416) in the Windows Ancillary Function Driver for WinSock, the kernel driver afd.sys that backs Windows sockets. Microsoft says a locally authenticated attacker can run a specially crafted application on an affected system, win a race condition, and gain SYSTEM privileges. No user interaction is needed.

Microsoft rates the attack complexity High because the attacker must win a race condition. The flaw is local only: it does not give initial access. It is an escalation step for an attacker who already runs code as a normal user. The CVSS 3.1 base score is 7.0.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
the host build is below the fixed build in the versions tableRun winver, or in PowerShell [System.Environment]::OSVersion.Version, or cmd /c ver. Compare the full build and revision (for example 10.0.19045.7663) with the versions table. Get-HotFix -Id KB5120249 (use the KB for your release) or wmic qfe list brief also works; a later cumulative update carries the fix, so compare builds when the KB is absent. Hosts on the hotpatch baseline report the earlier build in the table's fixed column, and are fixed.
an attacker already runs code on the host as a local userThis is a property of your environment (CVSS AV:L, PR:L: a local, authorized account). List who can sign in locally or by Remote Desktop: net localgroup "Remote Desktop Users", net localgroup Users and, on a shared host, query user to see live sessions. Hosts where many people run code (Remote Desktop session hosts, VDI pools, jump hosts, build agents) come first. Service accounts: Get-CimInstance Win32_Service | Where-Object { $_.StartName -notmatch 'LocalSystem|NT AUTHORITY' } | Select-Object Name, StartName lists services that run as ordinary accounts, and code execution in any of them is a local foothold. Application control state: Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard shows CodeIntegrityPolicyEnforcementStatus (1 is audit only, 2 is enforced), and Get-AppLockerPolicy -Effective lists AppLocker rules; a host with no enforced policy lets any local user run a crafted application.

Affected and fixed versions

Scroll the table sideways for more columns

Where Microsoft lists two KBs for one release (Server 2022, Windows 11 24H2 and 25H2, Server 2025), its release data marks the earlier build's KB as a Security Hotpatch Update and the later build's KB as the standard Security Update. Each carries the fix and each has its own fixed build in the table. NVD sets its affected threshold at the later build, so a hotpatched host on the earlier build still shows as below NVD's threshold even though Microsoft lists that build as fixed. The other releases list one KB. Microsoft's August 2026 release data lists 13 KB articles for this CVE in all. Windows 11 24H2 (build 26100.9168) and Windows Server 2025 (build 26100.33296) share the 26100 base build but ship on separate servicing streams, so their revision numbers differ; Microsoft's August 2026 release data lists each build against its own KB, and the table copies them.
Windows releaseAffected builds (NVD threshold)Fixed builds as Microsoft lists themUpdate (11 Aug 2026)
Windows Server 2012 (and Server Core)Earlier than 6.2.9200.262806.2.9200.26280KB5120386
Windows Server 2012 R2 (and Server Core)Earlier than 6.3.9600.233386.3.9600.23338KB5120385
Windows 10 Version 1607 and Windows Server 2016 (and Server Core)Earlier than 10.0.14393.941810.0.14393.9418KB5120418
Windows 10 Version 1809 and Windows Server 2019 (and Server Core)Earlier than 10.0.17763.912110.0.17763.9121KB5120238
Windows 10 Version 21H2 (32-bit, ARM64, x64)Earlier than 10.0.19044.766310.0.19044.7663KB5120249
Windows 10 Version 22H2 (32-bit, ARM64, x64)Earlier than 10.0.19045.766310.0.19045.7663KB5120249
Windows Server 2022 (and Server Core)Earlier than 10.0.20348.549910.0.20348.5440 (KB5120229) or 10.0.20348.5499 (KB5120242)KB5120229, KB5120242
Windows 11 Version 23H2 (ARM64, x64)Earlier than 10.0.22631.751710.0.22631.7517KB5120240
Windows 11 Version 24H2 (ARM64, x64)Earlier than 10.0.26100.916810.0.26100.9106 (KB5120994) or 10.0.26100.9168 (KB5121003)KB5120994, KB5121003
Windows 11 Version 25H2 (ARM64, x64)Earlier than 10.0.26200.916810.0.26200.9106 (KB5120994) or 10.0.26200.9168 (KB5121003)KB5120994, KB5121003
Windows 11 Version 26H1 (ARM64, x64)Earlier than 10.0.28000.270410.0.28000.2704KB5121000
Windows Server 2025 (and Server Core)Earlier than 10.0.26100.3329610.0.26100.33222 (KB5120228) or 10.0.26100.33296 (KB5120233)KB5120228, KB5120233

If the fix cannot go in yet

  • Install the August 2026 cumulative update, or a later one, for the release (see the versions table). Cost: a restart. This is the fix.
  • Microsoft lists no workaround. Because the attacker must already run code locally, patch the hosts where that is routine first: Remote Desktop session hosts, VDI pools, jump hosts and build agents. Cost: an earlier restart window for those hosts.

What to look for

  • Microsoft and CISA publish no log signature, file name or network indicator for this flaw, and CISA marks forensic triage as not required. The one artifact tied to the bug is the driver. Microsoft says the attacker must win a race, so an attempt that loses can leave a kernel crash. In the System log, Microsoft-Windows-WER-SystemErrorReporting event 1001 records each BugCheck. Open the dump (C:\Windows\MEMORY.DMP or C:\Windows\Minidump) in WinDbg and run !analyze -v: a faulting module or stack that names afd.sys on a host below the fixed build is a lead. The same crash on a patched host is a different fault. Start with hosts where several users run code.

Exploited on the day of disclosure, 11 Aug 2026.

Exploitation reported so far

Microsoft's first release of the advisory marks the flaw as exploited, and CISA lists it in KEV. KEV lists ransomware campaign use as Unknown. Neither Microsoft nor CISA names the actors or victims, and no report on the exploitation is cited.

Why attack-path analysis settles it

Exposure needs an unpatched build and an attacker who already runs code locally on that host. The build check settles the first. Because the flaw is local, an attack-path view of how an attacker gets local code on unpatched hosts decides real priority, and KEV shows it is already used.

Sources

  1. CVE-2026-68820: NVD record, read 19 Nov 2026
  2. CVE-2026-68820: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-68820: Microsoft advisory (MSRC CVRF, August 2026 release: fixed builds, KBs, Exploited: Yes, FAQs, acknowledgments), read 19 Nov 2026
  4. CVE-2026-68820: Microsoft advisory (MSRC API record), read 19 Nov 2026

Last reviewed 19 Nov 2026.