dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-45605

HIGH · 7.8 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 →
80/100
Remediation priority · High
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 Bluetooth Service 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 use-after-free vulnerability in the Windows Bluetooth Service allows an authorized local attacker to elevate privileges by exploiting improper memory management in the Bluetooth stack.

MitigationApply available Microsoft security updates for Windows when released. Verify that Bluetooth service is properly patched and monitor for any anomalies.

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

CVSS:3.1/AV:L/AC:L/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. Identify Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt to obtain the exact Windows build
    Affected if The version falls within any of the affected ranges: Windows 10 1607 < 10.0.14393.9234, 1809 < 10.0.17763.8880, 21h2 < 10.0.19044.7417, 22h2 < 10.0.19045.7417, or Windows 11 23h2 < 10.0.22631.7219, 24h2 < 10.0.26100.8655, 25h2 < 10.0.26200.8655, 26h1 < 10.0.28000.2269
  2. Verify Bluetooth Service status
    Run 'services.msc' and locate the "Bluetooth Support Service" or run 'sc query bthserv' in Command Prompt
    Affected if The Bluetooth Support Service is installed and running (the vulnerability exists within this service)
  3. Check for unexpected SYSTEM-privileged processes
    Open Task Manager, go to the Details tab, sort by User, and look for processes running as SYSTEM that were not launched by an administrator or scheduled task
    Affected if There are SYSTEM-privileged processes owned by the current user account or unknown origins that should not have elevation
  4. Review Security event logs for Bluetooth service anomalies
    Open Event Viewer, navigate to Windows Logs > Security, and filter for Event ID 4688 (new process creation) involving bthserv.exe or suspicious process spawns around the time of compromise
    Affected if Event logs show unusual process creation originating from Bluetooth service or attempts to spawn elevated processes from a non-elevated context

You are affected if your Windows version is below the patched build numbers AND the Bluetooth Support Service is enabled on your system.

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 available Microsoft security updates for Windows when released. Verify that Bluetooth service is properly patched and monitor for any anomalies.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9234 | Windows 10 1809: build 10.0.17763.8880 | Windows 10 21h2: build 10.0.19044.7417 | Windows 10 22h2: build 10.0.19045.7417 | Windows 11 23h2: build 10.0.22631.7219 | Windows 11 24h2: build 10.0.26100.8655 | Windows 11 25h2: build 10.0.26200.8655 | Windows 11 26

  1. Identify the current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Version"'
  2. Determine which Windows 10 or 11 version and build is currently installed
  3. Open Settings > Windows Update > Check for updates
  4. Install the latest cumulative security update for your specific Windows version
  5. Alternatively, manually download and install the appropriate KB from the Microsoft Update Catalog matching your Windows version (KB5055527 for the referenced builds)
  6. Restart the system after applying the update
  7. Verify the update was installed successfully by checking 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative update considerations apply - ensure backups and compatibility testing for critical systems before deployment

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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