dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-23671

HIGH · 7.0 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 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 Bluetooth RFCOM Protocol Driver 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 Bluetooth RFCOM Protocol Driver where improper synchronization during concurrent access to shared resources allows an authenticated local attacker to elevate privileges to higher permission levels.

MitigationApply vendor-supplied Windows security updates promptly; prioritize patching systems with Bluetooth enabled given the local attack vector.

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.8957
Windows 10 1809Operating system
Affected:< 10.0.17763.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719

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 or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to view the installed Windows build number
    Affected if The displayed build number is lower than any of these thresholds: 10.0.14393.8957 (Win10 1607), 10.0.17763.8511 (Win10 1809), 10.0.19044.7058 (Win10 21h2), 10.0.19045.7058 (Win10 22h2), 10.0.22631.6783 (Win11 23h2), 10.0.26100.7979 (Win11 24h2), 10.0.26200.7979 (Win11 25h2), 10.0.28000.1719 (Win11 2
  2. Verify Bluetooth is present
    Open Device Manager, expand 'Bluetooth', and confirm that a Bluetooth radio adapter is listed. Alternatively, run 'Get-PnpDevice -Class Bluetooth' in PowerShell
    Affected if A Bluetooth adapter is shown as present and enabled in the system
  3. Check Bluetooth driver version
    In Device Manager, right-click the Bluetooth RFCOM Protocol Driver (usually under 'Bluetooth' or 'Ports'), select Properties, go to the Driver tab, and note the driver version. Alternatively, run 'driverquery /v | findstr -i RFCOMM'
    Affected if The driver version is outdated and corresponds to an unpatched Windows build from step 1
  4. Confirm attacker needs local authentication
    Verify that untrusted users have physical or console access to the machine, as the vulnerability requires an authenticated local attacker
    Affected if Untrusted local users can log onto the system and execute concurrent Bluetooth operations

The system is likely affected if the Windows build number is below the thresholds listed AND a Bluetooth adapter is present and enabled.

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.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply vendor-supplied Windows security updates promptly; prioritize patching systems with Bluetooth enabled given the local attack vector.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.8957 or later | Windows 10 1809: build 10.0.17763.8511 or later | Windows 10 21h2: build 10.0.19044.7058 or later | Windows 10 22h2: build 10.0.19045.7058 or later | Windows 11 23h2: build 10.0.22631.6783 or later | Windows 11 24h2: build 10.0.26100.7979 or later |

  1. 1. Identify the current Windows version by running `winver` or `systeminfo` in Command Prompt
  2. 2. Determine the appropriate security update for your Windows version from Microsoft Update Catalog or Windows Update
  3. 3. Apply the corresponding security update: For Windows 10 1607, install KB5055523 (or later) containing build 10.0.14393.8957 | For Windows 10 1809, install KB5055525 (or later) containing build 10.0.17763.8511 | For Windows 10 21h2, install KB5055493 (or later) containing build 10.0.19044.7058 | For Windows 10 22h2, install KB5055520 (or later) containing build 10.0.19045.7058 | For Windows 11 2
  4. 4. Restart the system after applying the update
  5. 5. Verify the update was installed successfully by checking the installed updates list and confirming the build number matches or exceeds the fixed version

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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