dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-62213

HIGH · 7.0 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Use after free 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 · moderate confidence

Use after free vulnerability in the Windows Ancillary Function Driver (afd.sys) for WinSock allows a locally authorized attacker to elevate privileges to higher integrity levels by exploiting improper memory handling in the kernel-mode driver.

MitigationApply Microsoft security updates for CVE-2025-62213 once released; prioritize patching systems with exposure to untrusted users or processes.

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 1607Operating system
Affected:< 10.0.14393.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2008Operating system
Affected:all versions= r2

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 Windows build version
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number (e.g., 10.0.19045.6575)
    Affected if The build number is lower than the version listed for your Windows release in the affected versions list (e.g., below 10.0.19045.6575 for Windows 10 22h2)
  2. Check afd.sys file version
    Open Command Prompt and run 'driverquery /v /fo csv | findstr afd' or navigate to C:\Windows\System32\drivers\afd.sys, right-click and view Properties > Details to see the File Version (e.g., 10.0.19045.1)
    Affected if The afd.sys file version is older than the patched version for your Windows build (the patched version matches or exceeds the build number in the affected versions threshold)
  3. Verify security update installation
    Open Command Prompt and run 'wmic qfe list' or 'Get-HotFix | Sort-Object InstalledOn' to list installed hotfixes, then look for a May 2025 or later security update related to afd.sys or Winsock
    Affected if No recent security update for afd.sys or WinSock is listed in the installed updates, indicating the patch has not been applied
  4. Identify Windows Server 2008
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to confirm if the system is Windows Server 2008 or Server 2008 R2
    Affected if The system is Windows Server 2008 or Server 2008 R2, as all versions of these products are affected (no patch available)

A system is affected if it runs any Windows version with a build number lower than the threshold listed in the affected versions, or if it is Windows Server 2008/2008 R2, and no corresponding security update has been installed.

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.14393.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Apply Microsoft security updates for CVE-2025-62213 once released; prioritize patching systems with exposure to untrusted users or processes.

Recommended fix High confidence

Upgrade to the specific fixed build for your Windows version: 10.0.14393.8594 (Win10 1607), 10.0.17763.8027 (Win10 1809), 10.0.19044.6575 (Win10 21h2), 10.0.19045.6575 (Win10 22h2), 10.0.22631.6199 (Win11 23h2), 10.0.26100.7092 (Win11 24h2), 10.0.26200.7092 (Win11 25h2); migrate off Windows Server 2

  1. 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows version family you are running (10 1607, 10 1809, 10 21h2, 10 22h2, 11 23h2, 11 24h2, 11 25h2, or Server 2008)
  3. 3. For Windows 10 1607 systems: upgrade to build 10.0.14393.8594 or later via Windows Update or Microsoft Update Catalog
  4. 4. For Windows 10 1809 systems: upgrade to build 10.0.17763.8027 or later via Windows Update or Microsoft Update Catalog
  5. 5. For Windows 10 21h2 systems: upgrade to build 10.0.19044.6575 or later via Windows Update or Microsoft Update Catalog
  6. 6. For Windows 10 22h2 systems: upgrade to build 10.0.19045.6575 or later via Windows Update or Microsoft Update Catalog
  7. 7. For Windows 11 23h2 systems: upgrade to build 10.0.22631.6199 or later via Windows Update or Microsoft Update Catalog
  8. 8. For Windows 11 24h2 systems: upgrade to build 10.0.26100.7092 or later via Windows Update or Microsoft Update Catalog
Caveat Standard Windows update process has minimal risk; Windows Server 2008 has no supported upgrade path and requires migration to a supported server OS

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62213 — 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-62213 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