dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-45598

HIGH · 7.0 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.14393.9234 / 10.0.17763.8880 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 · moderate confidence

A race condition vulnerability exists in the Windows Ancillary Function Driver for WinSock (AFD.sys) where improper synchronization of shared resources allows a local authenticated attacker to elevate privileges to higher permission levels.

MitigationApply Microsoft security updates for Windows when released; until then, limit local access to trusted users only and monitor for suspicious privilege escalation activity.

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.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269

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 version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows build number
    Affected if The build number falls below any of these thresholds: 14393.9234 (Win10 1607), 17763.8880 (Win10 1809), 19044.7417 (Win10 21h2), 19045.7417 (Win10 22h2), 22631.7219 (Win11 23h2), 26100.8655 (Win11 24h2), 26200.8655 (Win11 25h2), or 28000.2269 (Win11 26h1)
  2. Check AFD.sys file version
    Open File Explorer, navigate to C:\Windows\System32\drivers\afd.sys, right-click, select Properties, and view the Details tab for the File version
    Affected if The file version is lower than the corresponding patched version for your Windows build, or the version field is empty or missing
  3. Verify Windows Update status
    Open Settings > Windows Update > Update history and look for recent security updates; alternatively, run 'systeminfo' and check the 'Hotfix(s)' field for KB entries related to 2026
    Affected if No recent security update containing CVE-2026-45598 fixes is listed in the update history, or the system has not been patched within the expected timeframe for this vulnerability

The system is affected if it is running a Windows version with a build number lower than the patched thresholds AND the AFD.sys file version does not reflect the security fix.

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.9234 / 10.0.17763.8880 / 10.0.19044.7417 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.19044.7417
Interim mitigation

Apply Microsoft security updates for Windows when released; until then, limit local access to trusted users only and monitor for suspicious privilege escalation activity.

Recommended fix High confidence

Apply the relevant Windows Security Update (KB patch) to reach the fixed build number for your Windows version

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest cumulative security updates
  3. After installation, verify the OS build number matches or exceeds the fixed version for your Windows release: Windows 10 1607 should be 10.0.14393.9234 or later; Windows 10 1809 should be 10.0.17763.8880 or later; Windows 10 21h2 should be 10.0.19044.7417 or later; Windows 10 22h2 should be 10.0.19045.7417 or later; Windows 11 23h2 should be 10.0.22631.7219 or later; Windows 11 24h2 should be 10.0
  4. To check the build number, run 'winver' from the Run dialog or 'systeminfo' from Command Prompt
  5. Restart the system if prompted to complete the update installation
Caveat Standard Windows update - no breaking changes expected for this security patch; as with any system update, ensure critical data is backed up before applying

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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