dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-62217

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
Concurrent execution using shared resource with improper synchronization ('race condition') 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 race condition vulnerability exists in the Windows Ancillary Function Driver for WinSock (AFD) where improper synchronization allows concurrent access to shared resources. An authorized local attacker can exploit this to elevate privileges to higher permission levels.

MitigationApply the relevant Microsoft security patch for this vulnerability once released. Until then, limit local privileged access and monitor for suspicious processes interacting with the AFD 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 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. Compare against the fixed builds: 14393.8594 (Win 10 1607), 17763.8027 (Win 10 1809), 19044.6575 (Win 10 21h2), 19045.6575 (Win 10 22h2), 22631.6199 (Win 11 23h2), 26100.7092 (Win 11 24h2), 26200.7092 (Win 11 25h2). For Server 2008 R2, all versions are affected.
    Affected if Your current build number is lower than the corresponding fixed build for your Windows version, or you are running any version of Windows Server 2008 R2.
  2. Check installed security updates
    Open Command Prompt and run 'wmic qfe list' or 'Get-HotFix | Sort-Object InstalledOn' to list installed updates. Look for the Microsoft security patch corresponding to CVE-2025-62217.
    Affected if The relevant security update for this CVE is not installed on the system.
  3. Verify AFD driver file version
    Navigate to C:\Windows\System32\drivers\afd.sys, right-click and select Properties, then view the Details tab to see the File Version. Alternatively, run 'driverquery /v | findstr afd' in Command Prompt.
    Affected if The afd.sys driver version is older than the version bundled in the patched security update for your Windows build.

Your system is affected if it runs an unpatched Windows version lower than the fixed build numbers listed, or if the CVE-2025-62217 security update is not 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 the relevant Microsoft security patch for this vulnerability once released. Until then, limit local privileged access and monitor for suspicious processes interacting with the AFD driver.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2025-62217 to reach the fixed build for your specific Windows version (e.g., 10.0.14393.8594 for Win10 1607, 10.0.17763.8027 for Win10 1809, etc.)

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows version and build you are running from the list of affected versions
  3. For Windows 10 1607 systems: Upgrade to build 10.0.14393.8594 or later
  4. For Windows 10 1809 systems: Upgrade to build 10.0.17763.8027 or later
  5. For Windows 10 21h2 systems: Upgrade to build 10.0.19044.6575 or later
  6. For Windows 10 22h2 systems: Upgrade to build 10.0.19045.6575 or later
  7. For Windows 11 23h2 systems: Upgrade to build 10.0.22631.6199 or later
  8. For Windows 11 24h2 systems: Upgrade to build 10.0.26100.7092 or later
Caveat Windows Server 2008 has no patch available; requires migration to supported Windows Server version

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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-62217 — 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-62217 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