CVSS 3.1
5.5 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVE-2026-96001 Windows Bluetooth Service Information Disclosure Vulnerability
Medium (5.5) in microsoft. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
On this page
Exposure of sensitive system information to an unauthorized control sphere in Windows Bluetooth Service allows an authorized attacker to disclose information locally.
Severity
- EPSS
- 0.5% estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- microsoft (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-96001 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96001?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96001?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-96001 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-96001)
HTML:
<a href="https://cve.bz/cve/CVE-2026-96001"><img src="https://cve.bz/cve/badge/CVE-2026-96001.svg" alt="CVE-2026-96001"></a>
Affected
- microsoft:windows 10 version 1607
- microsoft:windows 10 version 1809
- microsoft:windows 10 version 21h2
- microsoft:windows 10 version 22h2
- microsoft:windows 11 version 23h2
- microsoft:windows 11 version 24h2
- microsoft:windows 11 version 25h2
- microsoft:windows 11 version 26h1
- microsoft:windows 11 version 26h2
- microsoft:windows server 2016
- microsoft:windows server 2016 (server core installation)
- microsoft:windows server 2019
- microsoft:windows server 2019 (server core installation)
- microsoft:windows server 2022
- microsoft:windows server 2025
- microsoft:windows server 2025 (server core installation)
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Microsoft Windows 10 Version 1607 | from 10.0.14393.0 before 10.0.14393.9688 |
| Microsoft Windows 10 Version 1809 | from 10.0.17763.0 before 10.0.17763.9487 |
| Microsoft Windows 10 Version 21H2 | from 10.0.19044.0 before 10.0.19044.7846 |
| Microsoft Windows 10 Version 22H2 | from 10.0.19045.0 before 10.0.19045.7846 |
| Microsoft Windows 11 version 23H2 | from 10.0.22631.0 before 10.0.22631.7711 |
| Microsoft Windows 11 Version 23H2 | from 10.0.22631.0 before 10.0.22631.7711 |
| Microsoft Windows 11 Version 24H2 | from 10.0.26100.0 before 10.0.26100.9974 |
| Microsoft Windows 11 Version 25H2 | from 10.0.26200.0 before 10.0.26200.9974 |
| Microsoft Windows 11 version 26H1 | from 10.0.28000.0 before 10.0.28000.3501 |
| Microsoft Windows 11 Version 26H2 | from 10.0.26300.0 before 10.0.26300.9974 |
| Microsoft Windows Server 2016 | from 10.0.14393.0 before 10.0.14393.9688 |
| Microsoft Windows Server 2016 (Server Core installation) | from 10.0.14393.0 before 10.0.14393.9688 |
| Microsoft Windows Server 2019 | from 10.0.17763.0 before 10.0.17763.9487 |
| Microsoft Windows Server 2019 (Server Core installation) | from 10.0.17763.0 before 10.0.17763.9487 |
| Microsoft Windows Server 2022 | from 10.0.20348.0 before 10.0.20348.5870 |
| Microsoft Windows Server 2025 | from 10.0.26100.0 before 10.0.26100.33822 |
| Microsoft Windows Server 2025 (Server Core installation) | from 10.0.26100.0 before 10.0.26100.33822 |
Attack patterns (CAPEC)
- CAPEC-170 Web Application Fingerprinting Likelihood: High · Severity: Low
- CAPEC-694 System Location Discovery Likelihood: High · Severity: Very Low
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.