Skip to content
Server Security Center
KEVhigh7.8

CVE-2025-21418: Microsoft Windows Ancillary Function Driver for WinSock Heap-Based Buffer Overflow

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-02-11.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
2.1%
higher than 82.5% of all CVEs
Added to CISA KEV
2025-02-11
US federal due date 2025-03-04
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-21418 explained

CVE-2025-21418 is a heap-based buffer overflow in the Microsoft Windows Ancillary Function Driver for WinSock. A local attacker can use it to escalate privileges to SYSTEM. CISA lists it as known to be exploited, so affected Windows client and server systems should be patched promptly.

Impact

An attacker who already has low-privileged local access can gain SYSTEM privileges without user interaction. This gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system. CISA rates it as not automatable, so each attack needs manual steps. Attackers are known to exploit it. Whether it is used in ransomware campaigns is unknown.

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.19045.5487 (Windows 10 22H2), 10.0.22631.4890 (Windows 11 23H2), 10.0.26100.3194 (Windows 11 24H2) and 6.1.7601.27566 (Server 2008 R2 SP1). Each product has its own fixed build. The page lists 13 further products.

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

Official description

Microsoft Windows Ancillary Function Driver for WinSock contains a heap-based buffer overflow vulnerability that allows for privilege escalation, enabling a local attacker to gain SYSTEM privileges.

CISA required action: Apply mitigations per vendor instructions 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, x64
    Affected
    • < 10.0.10240.20915
    Fixed in
    • 10.0.10240.20915
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7785
    Fixed in
    • 10.0.14393.7785
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.6893
    Fixed in
    • 10.0.17763.6893
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5487
    Fixed in
    • 10.0.19044.5487
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5487
    Fixed in
    • 10.0.19045.5487
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4890
    Fixed in
    • 10.0.22621.4890
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4890
    Fixed in
    • 10.0.22631.4890
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4890
    Fixed in
    • 10.0.22631.4890
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.3194
    Fixed in
    • 10.0.26100.3194
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27566
    Fixed in
    • 6.1.7601.27566
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27566
    Fixed in
    • 6.1.7601.27566
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.23117
    Fixed in
    • 6.0.6003.23117
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.23117
    Fixed in
    • 6.0.6003.23117
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25317
    Fixed in
    • 6.2.9200.25317
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25317
    Fixed in
    • 6.2.9200.25317
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22417
    Fixed in
    • 6.3.9600.22417
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22417
    Fixed in
    • 6.3.9600.22417
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7785
    Fixed in
    • 10.0.14393.7785
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7785
    Fixed in
    • 10.0.14393.7785
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.6893
    Fixed in
    • 10.0.17763.6893
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.6893
    Fixed in
    • 10.0.17763.6893
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.3207
    Fixed in
    • 10.0.20348.3207
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1425
    Fixed in
    • 10.0.25398.1425
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.3194
    Fixed in
    • 10.0.26100.3194
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.3194
    Fixed in
    • 10.0.26100.3194

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.20915
    • Microsoft Windows 10 Version 1607: 10.0.14393.7785
    • Microsoft Windows 10 Version 1809: 10.0.17763.6893
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5487
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5487
    • Microsoft Windows 11 version 22H2: 10.0.22621.4890
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21418
  • CISA's deadline for US federal agencies: 2025-03-04 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to at least the fixed build listed for its Windows version.
  2. Prioritize patching because CISA lists this vulnerability as known exploited. The US federal due date was 2025-03-04.
  3. Follow the Microsoft advisory for products not shown here, including the further listed products.
  4. Limit local and interactive logon rights to reduce the number of accounts that could attempt privilege escalation.
  5. Check systems for signs of compromise, such as unexpected SYSTEM-level processes or new privileged 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-122 Heap-based Buffer Overflow

Questions about CVE-2025-21418

Can this be exploited remotely?
No. The attack vector is local. An attacker needs low-privileged access to the system first and can then escalate to SYSTEM privileges.
Is CVE-2025-21418 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-02-11. Whether it is used in ransomware is unknown.
Which build fixes Windows 11 24H2?
The CVE record names 10.0.26100.3194 as the fixed build for Microsoft Windows 11 Version 24H2 on ARM64 and x64.

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.