Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain unsupervised physical device access
-
DeliveryInterface with device hardware or firmware layer
-
ExploitExploit BitLocker protection mechanism failure (CWE-693)
-
ExecutionBypass encryption boundary without credentials
-
ImpactRead encrypted volume contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
|
| Exploitation Conditions | Physical presence at the target device is strictly required, as the CVSS attack vector AV:P (Physical) confirms this is not remotely exploitable under any network condition. The attacker requires no prior authentication (PR:N) and no user interaction (UI:N), meaning the device does not need to be powered on, logged in, or unlocked by the legitimate user at time of attack. The specific hardware interaction technique required to trigger the protection mechanism failure is not disclosed in available public data - the precise method (TPM communication interception, pre-boot environment manipulation, or other physical vector) remains unconfirmed from this intelligence. What limits exploitation: the absolute requirement for physical device access eliminates all remote and network-adjacent attack scenarios; server hardware in locked data centers with monitored physical access has substantially reduced realistic exposure. What does NOT limit exploitation: no authentication, no special software configuration, and no specific OS state appears required based on the PR:N/UI:N/AC:L vector components. |
| Impact | The CVSS base score of 5.3 (Medium) is shaped primarily by the physical attack vector (AV:P), which substantially limits the realistic attacker pool to adversaries with direct hands-on access to the device. The Changed Scope elevation partially offsets this mitigating factor by acknowledging the serious cross-boundary confidentiality impact. No EPSS data was provided in the available intelligence, and this CVE is not listed in CISA KEV, confirming no verified active exploitation at time of analysis. No public POC has been identified. Despite the medium CVSS score, real-world risk to organizations deploying BitLocker specifically for its intended use case - protecting lost, stolen, or physically accessible devices - is meaningfully higher: the entire threat model that BitLocker defends against centers on physical access scenarios. Enterprises with laptops in the field, shared workstations, or hardware deployed in uncontrolled environments (branch offices, retail, healthcare kiosks) face elevated practical risk and should prioritize patching accordingly. Servers in locked data centers have substantially lower exposure. |
| Exploit ScenarioDerived | A threat actor with physical access to an unattended Windows laptop - obtained via theft, loss, or an evil maid attack in an unsupervised location such as a hotel room or open office - exploits the BitLocker protection mechanism failure to read the contents of the encrypted volume without knowledge of the BitLocker PIN, recovery key, or user credentials. Leveraging the low attack complexity (AC:L) and no-privileges-required (PR:N) conditions, the attacker interfaces directly with the device hardware, circumventing the encryption boundary and accessing sensitive organizational data, personal files, or credentials stored on disk. No public exploit code has been identified at time of analysis, and the specific physical technique (e.g., TPM bus sniffing, DMA attack, cold boot) has not been confirmed from available intelligence. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 09, 2026
BitLocker drive encryption on Windows can be bypassed by a physically present, unauthenticated attacker, exposing protected volume contents with high confidentiality impact. Classified as CWE-693 (Protection Mechanism Failure), the flaw undermines BitLocker's core threat model - data-at-rest protection - across a wide range of Windows 10, Windows 11, and Windows Server releases from 2012 through 2025. No public exploit has been identified at time of analysis, and Microsoft has released patches for all affected versions; however, the physical access requirement means organizations with mobile or physically accessible systems should treat this as a higher operational priority than the CVSS score alone implies.
RemediationAI
Apply the vendor-released patches from Microsoft targeting each affected Windows build. Specific patched versions confirmed from EUVD-2026-35695 include: Windows 10 22H2 to build 10.0.19045.7417, Windows 11 24H2 to build 10.0.26100.8655, Windows 11 26H1 to build 10.0.28000.2269, Windows Server 2025 to build 10.0.26100.32995, Windows Server 2022 to build 10.0.20348.5256, and Windows Server 2019 to build 10.0.17763.8880, among others. Consult the full advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45655 for the complete patched build list. As compensating controls prior to patching, enforce BitLocker with TPM+PIN or TPM+USB key multi-factor pre-boot authentication rather than TPM-only mode, since requiring a PIN or external key at boot reduces the attack surface for physical bypass - note this adds operational overhead for remote reboots and headless servers. Implement strict physical access controls including device cable locks, locked storage for unattended hardware, and asset tracking for mobile devices; these do not eliminate the vulnerability but reduce attacker opportunity. For high-sensitivity environments, consider BitLocker Network Unlock as an additional layer, though this requires reliable network connectivity at boot.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 34 packages in microsoft, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
BitLocker is Microsoft's full-volume encryption feature designed to protect data at rest by encrypting entire disk volumes, with TPM-based key storage as the common deployment model. The vulnerability is classified as CWE-693 (Protection Mechanism Failure), indicating the encryption protection boundary itself fails under specific physical access conditions rather than a cryptographic weakness in the underlying algorithm. The CVSS vector AV:P confirms a hands-on physical attack is required. The Changed Scope component (S:C) in the vector is significant: it indicates the exploit crosses a defined security boundary - most likely from the pre-boot hardware or firmware layer into the encrypted operating system or data partition - without requiring any credentials (PR:N). The Confidentiality:High and Integrity:None/Availability:None profile is consistent with a read-only bypass of encrypted storage, meaning attackers can extract data but cannot silently modify it through this vector alone.
Know when Windows 10 1607 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Sources disagree (Medium–Critical)AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Protection mechanism failure in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-35695
GHSA-cmfc-3q8r-88w2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB