CVE-2025-32709: Microsoft Windows Ancillary Function Driver for WinSock Use-After-Free
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-05-13.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 1.8%
- higher than 79.2% of all CVEs
- Added to CISA KEV
- 2025-05-13
- US federal due date 2025-06-03
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-32709 explained
CVE-2025-32709 is a privilege escalation flaw in the Windows Ancillary Function Driver for WinSock. The record classifies it as a use-after-free (CWE-416), while the description calls it a null pointer dereference. An authorized local attacker can use it to gain elevated privileges. CISA lists it as known to be exploited, so patching should be prioritized.
Impact
An attacker who can already log on with low privileges can elevate privileges locally. No user interaction is needed, and attack complexity is low. Successful exploitation has high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system component. CISA rates it as not automatable. The flaw cannot be exploited remotely without local access.
Who is affected
The CVE record lists Windows 10 Versions 1507, 1607, 1809, 21H2 and 22H2; Windows 11 versions 22H2, 22H3, 23H2 and 24H2; and Windows Server 2008 R2 SP1 (including Server Core) and Server 2008 SP2. Fixed builds include 10.0.10240.21014, 10.0.14393.8066, 10.0.17763.7314, 10.0.19044.5854, 10.0.19045.5854, 10.0.22621.5335, 10.0.22631.5335, 10.0.26100.4061, 6.1.7601.27730 and 6.0.6003.23317. Further products are listed on this page.
Written with AI from the data on this page and checked against it automatically.
Official description
Null pointer dereference in Windows Ancillary Function Driver for WinSock allows an authorized attacker to elevate privileges locally.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 150732-bit, x64AffectedFixed in
- < 10.0.10240.21014
- 10.0.10240.21014
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.8066
- 10.0.14393.8066
- Microsoft Windows 10 Version 180932-bit, x64AffectedFixed in
- < 10.0.17763.7314
- 10.0.17763.7314
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.5854
- 10.0.19044.5854
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.5854
- 10.0.19045.5854
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.5335
- 10.0.22621.5335
- Microsoft Windows 11 version 22H3ARM64AffectedFixed in
- < 10.0.22631.5335
- 10.0.22631.5335
- Microsoft Windows 11 Version 23H2x64AffectedFixed in
- < 10.0.22631.5335
- 10.0.22631.5335
- Microsoft Windows 11 Version 24H2ARM64, x64AffectedFixed in
- < 10.0.26100.4061
- 10.0.26100.4061
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- < 6.1.7601.27730
- 6.1.7601.27730
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H3ARM64 |
|
|
| Microsoft Windows 11 Version 23H2x64 |
|
|
| Microsoft Windows 11 Version 24H2ARM64, x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
Show 15 more products
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64AffectedFixed in
- < 6.1.7601.27730
- 6.1.7601.27730
- Microsoft Windows Server 2008 Service Pack 232-bit, x64AffectedFixed in
- < 6.0.6003.23317
- 6.0.6003.23317
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64AffectedFixed in
- < 6.0.6003.23317
- 6.0.6003.23317
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.25475
- 6.2.9200.25475
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.25475
- 6.2.9200.25475
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.22577
- 6.3.9600.22577
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.22577
- 6.3.9600.22577
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.8066
- 10.0.14393.8066
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.8066
- 10.0.14393.8066
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.7314
- 10.0.17763.7314
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.7314
- 10.0.17763.7314
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.3692
- 10.0.20348.3692
- Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64AffectedFixed in
- < 10.0.25398.1611
- 10.0.25398.1611
- Microsoft Windows Server 2025x64AffectedFixed in
- < 10.0.26100.4061
- 10.0.26100.4061
- Microsoft Windows Server 2025 (Server Core installation)x64AffectedFixed in
- < 10.0.26100.4061
- 10.0.26100.4061
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 232-bit, x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2025x64 |
|
|
| Microsoft Windows Server 2025 (Server Core installation)x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1507: 10.0.10240.21014
- Microsoft Windows 10 Version 1607: 10.0.14393.8066
- Microsoft Windows 10 Version 1809: 10.0.17763.7314
- Microsoft Windows 10 Version 21H2: 10.0.19044.5854
- Microsoft Windows 10 Version 22H2: 10.0.19045.5854
- Microsoft Windows 11 version 22H2: 10.0.22621.5335
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-32709
- CISA's deadline for US federal agencies: 2025-06-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each system to the fixed build for its Windows version.
- Prioritize systems where many users can log on, such as servers and shared workstations.
- Verify the installed build number on each host matches or exceeds the fixed version.
- Restrict local and interactive logon rights to users who need them.
- Review hosts for signs of unexpected privilege escalation or compromise.
- Follow CISA's required action; discontinue use of the product if mitigations are unavailable.
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-2025-32709
- Is CVE-2025-32709 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-05-13, with a US federal due date of 2025-06-03. Whether it is used in ransomware campaigns is unknown.
- Can it be exploited remotely?
- No. The attack vector is local, and the attacker needs low-privileged access to the system first. It allows privilege elevation, not initial access.
- Which update fixes it?
- The CVE record lists a fixed build for each affected Windows version, for example
10.0.26100.4061for Windows 11 Version 24H2 and10.0.19045.5854for Windows 10 Version 22H2. Install Microsoft's security update for your version.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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.