dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Jun 2025.
Windows 10 1507Operating system · Microsoft

CVE-2025-32709

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Null pointer dereference in Windows Ancillary Function Driver for WinSock allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A null pointer dereference vulnerability exists in Windows Ancillary Function Driver for WinSock (AFD.sys), a kernel-mode network driver. An authorized local attacker can exploit this flaw to elevate privileges to SYSTEM level by triggering the null pointer dereference through specially crafted WinSock operations.

MitigationApply the Microsoft security update for CVE-2025-32709 via Windows Update or enterprise patch management systems to patch the vulnerable AFD.sys driver.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.3981

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check AFD.sys file version
    Open an elevated command prompt and run: `dir /a C:\Windows\System32\drivers\afd.sys`. Note the file version shown in the output, then compare it against the fixed versions for your Windows build (e.g., 10.0.19045.5854 for Win10 22h2, 10.0.22621.5335 for Win11 22h2, etc.).
    Affected if The file version is lower than the fixed version for your specific Windows build and edition.
  2. Confirm Windows build number
    Run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to identify your exact Windows build and version (e.g., 19045 for Win10 22h2, 22621 for Win11 22h2).
    Affected if Your Windows build falls within the affected version ranges and is below the patched builds listed in the CVE.
  3. Check for recent security updates
    Run `powershell Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10` to list recently installed security updates.
    Affected if No security update matching May 2025 or later (CVE-2025-32709 patch month) is installed.
  4. Verify driver is loaded
    Run `driverquery /v | findstr -i afd` to confirm the AFD.sys driver is loaded and active on the system.
    Affected if The driver is present and loaded (which is default for any Windows system with networking enabled).

You are affected if your Windows build version is lower than the fixed build for your release channel AND you have not installed the May 2025 security update that addresses CVE-2025-32709.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply the Microsoft security update for CVE-2025-32709 via Windows Update or enterprise patch management systems to patch the vulnerable AFD.sys driver.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21014 or later | Windows 10 1607: 10.0.14393.8066 or later | Windows 10 1809: 10.0.17763.7314 or later | Windows 10 21h2: 10.0.19044.5854 or later | Windows 10 22h2: 10.0.19045.5854 or later | Windows 11 22h2: 10.0.22621.5335 or later | Windows 11 23h2: 10.0.22631.5335 or

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 version is installed (1507, 1607, 1809, 21h2, 22h2, 11 22h2, 11 23h2, or 11 24h2)
  3. Open Windows Settings > Windows Update > Check for updates
  4. Install all available security updates from Microsoft Update
  5. Alternatively, manually install the corresponding KB update for your Windows version from the Microsoft Update Catalog
  6. Restart the system after updates are installed
  7. Verify the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update with no expected breaking changes; may require system restart

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32709 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data