dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32161

HIGH · 7.5 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.14393.9140 / 10.0.17763.8755 or later.
See remediation →
80/100
Remediation priority · High
No privileges 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 Native WiFi Miniport Driver allows an unauthorized attacker to execute code over an adjacent network.

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 Native WiFi Miniport Driver where concurrent execution with improper synchronization allows an adjacent network attacker to execute arbitrary code by exploiting shared resource access patterns.

MitigationApply the relevant Microsoft security update for the Windows WiFi Miniport Driver to address the race condition; verify WiFi functionality post-patch.

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.9140
Windows 10 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113

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

CVSS:3.1/AV:A/AC:H/PR:N/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
    Run 'winver' from command prompt or check System Properties to see the OS Build number, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The build number falls below any of these thresholds: 14393.9140 (Win10 1607), 17763.8755 (Win10 1809), 19044.7291 (Win10 21h2/22h2), 22631.7079 (Win11 23h2), 26100.8390 (Win11 24h2), 26200.8390 (Win11 25h2), or 28000.2113 (Win11 26h1)
  2. Verify WiFi capability is present
    Open Device Manager, expand 'Network adapters' and look for any WiFi or Wireless adapter listed, or run 'netsh wlan show interfaces'
    Affected if A WiFi adapter is present and enabled on the system
  3. Confirm WiFi driver is loaded
    Run 'netsh wlan show drivers' to check if a wireless LAN interface driver is reported as loaded and ready
    Affected if The WiFi driver reports as loaded and the interface is active
  4. Check driver file version (optional)
    Locate the WiFi Miniport driver in Device Manager under Network adapters, right-click and select Properties, then view the Driver tab for file version details
    Affected if The driver version cannot be determined or is older than the patched builds for your Windows version

A system is affected if it runs an unpatched Windows build within the affected version ranges AND has an active WiFi adapter with the Native WiFi Miniport Driver loaded.

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.9140 / 10.0.17763.8755 / 10.0.19044.7291 or later
Fixed in 10.0.14393.914010.0.17763.875510.0.19044.7291
Interim mitigation

Apply the relevant Microsoft security update for the Windows WiFi Miniport Driver to address the race condition; verify WiFi functionality post-patch.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.9140 or later | Windows 10 1809: 10.0.17763.8755 or later | Windows 10 21h2: 10.0.19044.7291 or later | Windows 10 22h2: 10.0.19045.7291 or later | Windows 11 23h2: 10.0.22631.7079 or later | Windows 11 24h2: 10.0.26100.8390 or later | Windows 11 25h2: 10.0.26200.8390 or

  1. Identify the current Windows version by running 'winver' or checking System Information
  2. Determine which Windows 10 or 11 version/build is currently installed
  3. Apply Windows Updates to install the latest security patches from Microsoft Update, which will include the fix for this vulnerability
  4. Alternatively, download and install the specific cumulative update for your Windows version that contains build number >= the fixed version for your release (e.g., for Windows 10 22h2, install update containing build 10.0.19045.7291 or later)
  5. Verify the update was successful by checking the OS build number again
Caveat Standard Windows update considerations - ensure backups of critical data before applying updates; some enterprise environments may require testing updates before broad deployment

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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