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

Published Feb 11, 2025
·
Updated

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.

Other sources

Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability

Microsoft

Affected Software

64 affected componentsFixes available
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2016
Microsoft Windows Server 2016
Microsoft Windows
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008 R2
Microsoft Windows 10 1607<10.0.10240.20915
Microsoft Windows 10 1607<10.0.10240.20915
Microsoft Windows 10 1809<10.0.17763.6893
Microsoft Windows 10 1809<10.0.17763.6893
Microsoft Windows 10 21h2<10.0.19044.5487
Microsoft Windows 10 22h2<10.0.19045.5487
Microsoft Windows 11 22h2<10.0.22621.4890
Microsoft Windows 11 23h2<10.0.22631.4890
Microsoft Windows 11 24h2<10.0.26100.3107
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.7785
Microsoft Windows Server 2019<10.0.17763.6893
Microsoft Windows Server 2022<10.0.20348.3148
Microsoft Windows Server 2022 23h2<10.0.25398.1425
Microsoft Windows Server 2025<10.0.26100.3107
Microsoft Windows Server 2008<6.0.6003.23117
6.0.6003.23117
Microsoft Windows Server 2008 R2<6.1.7601.27566
6.1.7601.27566
Microsoft Windows Server 2012 R2<6.3.9600.22417
6.3.9600.22417
Microsoft Windows Server 2008<6.0.6003.23117
6.0.6003.23117
Microsoft Windows Server 2016<10.0.14393.7785
10.0.14393.7785
Microsoft Windows Server 2008<6.0.6003.23117
6.0.6003.23117
Microsoft Windows Server 2008<6.0.6003.23117
6.0.6003.23117
Microsoft Windows Server 2008 R2<6.1.7601.27566
6.1.7601.27566
Microsoft Windows Server 2016<10.0.14393.7785
10.0.14393.7785
Microsoft Windows 10=1607
10.0.14393.7785
Microsoft Windows Server 2012<6.2.9200.25317
6.2.9200.25317
Microsoft Windows Server 2012 R2<6.3.9600.22417
6.3.9600.22417
Microsoft Windows 10=1607
10.0.14393.7785
Microsoft Windows Server 2012<6.2.9200.25317
6.2.9200.25317
Microsoft Windows 10<10.0.10240.20915
10.0.10240.20915
Microsoft Windows 10<10.0.10240.20915
10.0.10240.20915
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.1425
10.0.25398.1425
Microsoft Windows 11=23H2
10.0.22631.4890
Microsoft Windows 11=24H2
10.0.26100.319410.0.26100.3107
Microsoft Windows Server 2025<10.0.26100.3194, <10.0.26100.3107
10.0.26100.319410.0.26100.3107
Microsoft Windows 11=24H2
10.0.26100.319410.0.26100.3107
Microsoft Windows 11=23H2
10.0.22631.4890
Microsoft Windows 10=22H2
10.0.19045.5487
Microsoft Windows 10=22H2
10.0.19045.5487
Microsoft Windows 11=22H2
10.0.22621.4890
Microsoft Windows Server 2025<10.0.26100.3194, <10.0.26100.3107
10.0.26100.319410.0.26100.3107
Microsoft Windows 10=22H2
10.0.19045.5487
Microsoft Windows 10=21H2
10.0.19044.5487
Microsoft Windows 11=22H2
10.0.22621.4890
Microsoft Windows 10=21H2
10.0.19044.5487
Microsoft Windows 10=21H2
10.0.19044.5487
Microsoft Windows Server 2022<10.0.20348.3207, <10.0.20348.3148
10.0.20348.320710.0.20348.3148
Microsoft Windows Server 2019<10.0.17763.6893
10.0.17763.6893
Microsoft Windows Server 2022<10.0.20348.3207, <10.0.20348.3148
10.0.20348.320710.0.20348.3148
Microsoft Windows 10=1809
10.0.17763.6893
Microsoft Windows Server 2019<10.0.17763.6893
10.0.17763.6893
Microsoft Windows 10=1809
10.0.17763.6893

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.0.6003.23117Patch KB5052072
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.1.7601.27566Patch KB5052032
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.7785Patch KB5052006
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.22417Patch KB5052042
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.25317Patch KB5052020
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.10240.20915Patch KB5052040
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.25398.1425Patch KB5051980
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.4890Patch KB5051989
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.3194Fixed in 10.0.26100.3107Patch KB5052105
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.5487Patch KB5051974
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22621.4890Patch KB5051989
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.5487Patch KB5051974
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.3207Fixed in 10.0.20348.3148Patch KB5052106
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.6893Patch KB5052000

Event History

Feb 11, 2025
CVE Published
via CISA·12:00 AM
Known Exploited
via CISA·12:00 AM
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Description
CVE Published
via MITRE·05:58 PM
Data Sourced
via MITRE·05:58 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
News Published
via Dark Reading·09:55 PM
News Published
via Dark Reading·10:24 PM
Feb 12, 2025
News Published
via The Register·02:58 AM
News Published
via ZDNet·05:29 PM
News Published
via ZDNet·06:28 PM
Feb 16, 2025
News Published
via The Register·03:01 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-21418?

CVE-2025-21418 has a high severity rating due to its heap-based buffer overflow vulnerability, which allows for privilege escalation.

2

How do I fix CVE-2025-21418?

To fix CVE-2025-21418, apply the latest security patch provided by Microsoft for the affected Windows versions.

3

Which versions of Windows are affected by CVE-2025-21418?

CVE-2025-21418 affects several versions of Windows, including Windows 11, various Windows Server editions, and specific builds of Windows 10.

4

What type of vulnerability is CVE-2025-21418?

CVE-2025-21418 is categorized as an elevation of privilege vulnerability due to a heap-based buffer overflow in the Ancillary Function Driver for WinSock.

5

Who is impacted by CVE-2025-21418?

Local attackers on vulnerable systems can exploit CVE-2025-21418 to gain SYSTEM privileges, making it critical for system administrators to address.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203