Microsoft Bluetooth Driver: Use after free allows local privilege escalation

Summary

A use-after-free vulnerability in the Microsoft Windows Bluetooth driver allows an authorized local attacker to elevate privileges. The attacker needs a valid low-privileged user session on the affected system, so the flaw is not reachable remotely from the internet. A successful attack gives the attacker higher privileges with high impact on confidentiality, integrity and availability.

Affected

• Windows 10 Version 1607 and Windows Server 2016 (including Server Core): builds before 10.0.14393.9688
• Windows 10 Version 1809 and Windows Server 2019 (including Server Core): builds before 10.0.17763.9487
• Windows 10 Version 21H2: builds before 10.0.19044.7846
• Windows 10 Version 22H2: builds before 10.0.19045.7846
• Windows 11 Version 23H2: builds before 10.0.22631.7711
• Windows 11 Version 24H2: builds before 10.0.26100.9974
• Windows 11 Version 25H2: builds before 10.0.26200.9974
• Windows 11 Version 26H1: builds before 10.0.28000.3501
• Windows 11 Version 26H2: builds before 10.0.26300.9974
• Windows Server 2022: builds before 10.0.20348.5870

Fixed in

Install the November 2026 security update from Microsoft for the affected Windows version. Fixed builds are listed in the Microsoft advisory, which maps the update packages to each system.

Workaround

Unknown. Microsoft lists no workaround. Where Bluetooth is not required, disabling the Bluetooth adapter or service reduces exposure; this is a general suggestion and not a vendor recommendation.

Exploitation

• Microsoft's advisory data shows no known exploitation and no public disclosure at the time of research.
• CISA SSVC: exploitation none, not automatable, total technical impact.
• No public proof of concept found.

Our recommendation

• Deploy the November 2026 cumulative update on all affected Windows systems through the normal Patch Tuesday cycle, starting with older or unsupported Windows 10 builds.
• Check whether Windows 10 devices are still receiving security updates, for example through Extended Security Updates.
• Where Bluetooth is not needed, disable it through policy.
• Prioritise shared PCs, terminal servers and endpoints where staff run untrusted files.

Public exploits iAttack code is publicly available (PoC on GitHub, Metasploit or Exploit-DB).

PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.

Research sources

• Microsoft Security Update Guide: CVE-2026-70120 msrc.microsoft.com
• CVE Record CVE-2026-70120 www.cve.org
• Rapid7: Patch Tuesday November 2026 www.rapid7.com

Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 11 Nov 2026, 08:15.