Skip to content
Server Security Center
KEVhigh7.0

CVE-2026-68820: Microsoft Windows Ancillary Function Driver for WinSock Use-After-Free

Microsoft Windows Ancillary Function Driver for WinSock · listed in the CISA catalog of actively exploited vulnerabilities since 2026-08-11.

CVSS v3.1 (CVE record)
7.0
high
EPSS (exploit probability, 30 days)
8.6%
higher than 95.1% of all CVEs
Added to CISA KEV
2026-08-11
US federal due date 2026-08-25
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-68820 explained

CVE-2026-68820 is a use-after-free flaw in the Windows Ancillary Function Driver for WinSock. An authorized local attacker can use it to elevate privileges on affected Windows 10, Windows 11 and Windows Server 2012 systems. CISA lists it as known exploited, so patching should be a priority.

Impact

An attacker who already has low-privileged local access can elevate privileges without user interaction. Successful exploitation affects confidentiality, integrity and availability at a high level. CISA rates the technical impact as total, meaning full control of the affected component. Attack complexity is high and CISA rates it as not automatable, so it cannot be exploited at scale without manual steps. CISA lists it as known exploited; ransomware use is unknown.

Who is affected

The CVE record lists Windows 10 Version 1607 (fixed in 10.0.14393.9418), 1809 (10.0.17763.9121), 21H2 (10.0.19044.7663) and 22H2 (10.0.19045.7663). Windows 11 version 23H2 is fixed in 10.0.22631.7517, 24H2 in 10.0.26100.9168, 25H2 in 10.0.26200.9168 and 26H1 in 10.0.28000.2704. Windows Server 2012, including Server Core, is fixed in 6.2.9200.26280, and Server 2012 R2, including Server Core, in 6.3.9600.23338. Earlier builds are affected. The page lists 7 further products.

Written with AI from the data on this page and checked against it automatically.

Official description

Use after free in Windows Ancillary Function Driver for WinSock allows an authorized attacker to elevate privileges locally.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.9418
    Fixed in
    • 10.0.14393.9418
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.9121
    Fixed in
    • 10.0.17763.9121
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.7663
    Fixed in
    • 10.0.19044.7663
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.7663
    Fixed in
    • 10.0.19045.7663
  • Microsoft Windows 11 version 23H2ARM64, x64
    Affected
    • < 10.0.22631.7517
    Fixed in
    • 10.0.22631.7517
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.9168
    Fixed in
    • 10.0.26100.9168
  • Microsoft Windows 11 Version 25H2ARM64, x64
    Affected
    • < 10.0.26200.9168
    Fixed in
    • 10.0.26200.9168
  • Microsoft Windows 11 version 26H1ARM64, x64
    Affected
    • < 10.0.28000.2704
    Fixed in
    • 10.0.28000.2704
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.26280
    Fixed in
    • 6.2.9200.26280
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.26280
    Fixed in
    • 6.2.9200.26280
Show 9 more products
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.23338
    Fixed in
    • 6.3.9600.23338
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.23338
    Fixed in
    • 6.3.9600.23338
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.9418
    Fixed in
    • 10.0.14393.9418
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.9418
    Fixed in
    • 10.0.14393.9418
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.9121
    Fixed in
    • 10.0.17763.9121
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.9121
    Fixed in
    • 10.0.17763.9121
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.5499
    Fixed in
    • 10.0.20348.5499
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.33296
    Fixed in
    • 10.0.26100.33296
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.33296
    Fixed in
    • 10.0.26100.33296

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1607: 10.0.14393.9418
    • Microsoft Windows 10 Version 1809: 10.0.17763.9121
    • Microsoft Windows 10 Version 21H2: 10.0.19044.7663
    • Microsoft Windows 10 Version 22H2: 10.0.19045.7663
    • Microsoft Windows 11 version 23H2: 10.0.22631.7517
    • Microsoft Windows 11 Version 24H2: 10.0.26100.9168
    Fixed versions for 13 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-68820
  • CISA's deadline for US federal agencies: 2026-08-25 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install Microsoft's security update that brings each system to at least the fixed build listed for its Windows version.
  2. Prioritize systems where many users have local or remote logon access, such as shared servers and terminal hosts.
  3. Follow the vendor advisory and CISA's required action; discontinue use of the product if mitigations are unavailable.
  4. Limit local logon rights and remove unneeded low-privileged accounts to reduce who can attempt privilege escalation.
  5. Check systems for signs of compromise, such as unexpected privilege changes or new administrative accounts.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

Questions about CVE-2026-68820

Can this be exploited remotely?
No. The attack vector is local, and the attacker needs low-privileged access to the system first. The flaw lets them elevate privileges on that system.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-08-11, with a US federal due date of 2026-08-25. Whether it is used in ransomware campaigns is unknown.
Which build fixes Windows 11 Version 24H2?
The CVE record names 10.0.26100.9168 as the fixed build for Windows 11 Version 24H2. Earlier builds are affected.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.