Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain physical access to device
-
DeliveryInteract with boot or hardware interface
-
ExploitBypass BitLocker protection mechanism
-
ExecutionUnseal volume master key
-
PersistRead or tamper with encrypted volume
-
ImpactExfiltrate sensitive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires physical access to a Windows device with BitLocker Drive Encryption enabled, consistent with the CVSS AV:L vector and the description's explicit 'physical attack' wording; remote exploitation is not in scope. The PR:L component indicates the attacker also needs some low-level privilege or local context (e.g., an existing local user session, ability to boot the device, or hardware-level interaction such as connecting to an exposed bus/port), so a fully powered-off device protected with TPM+PIN pre-boot authentication and disabled DMA ports materially limits exploitability. UI:N means no user interaction is required once physical access is obtained, making unattended, stolen, or lost devices the realistic target population rather than devices in continuously supervised environments. |
| Impact | The CVSS 7.8 vector (AV:L/AC:L/PR:L/UI:N) describes a local attack with low complexity requiring low privileges and no user interaction, with high CIA impact - consistent with the description's 'physical attack' framing, where the attacker has hands-on access to the device. EPSS data is not provided, and the vulnerability is not on the CISA KEV list at time of analysis, so there is no public exploit identified at time of analysis. Real-world risk is concentrated on portable, easily-stolen, or unattended endpoints (laptops, kiosks, field devices) and on threat models where physical possession is realistic - corporate fleet theft, evil-maid attacks, lost devices, and supply-chain or border-inspection scenarios. For purely datacenter or physically-controlled assets, residual risk is meaningfully lower; the CVSS score therefore overstates risk for some deployments and understates it for high-mobility fleets. |
| Exploit ScenarioDerived | An attacker who obtains physical possession of a powered-off or locked Windows laptop - for example through theft, an evil-maid scenario, or temporary unattended access during travel - manipulates the boot environment or hardware interfaces to bypass BitLocker's protection mechanism and read or modify the supposedly encrypted volume. Because the CVSS vector is AV:L with low complexity and the description explicitly notes a physical attack, the scenario is realistic for any unattended Windows endpoint with BitLocker as the sole at-rest protection. No public proof-of-concept has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 09, 2026
Security feature bypass in Microsoft Windows BitLocker allows an attacker with physical access to circumvent the drive encryption protection mechanism. Affected systems can have BitLocker-protected data accessed despite the encryption-at-rest control being enabled, undermining a core platform confidentiality boundary. There is no public exploit identified at time of analysis, but the vulnerability is reported by Microsoft (secure@microsoft.com) as a protection mechanism failure with high impact across confidentiality, integrity, and availability.
RemediationAI
Apply the Microsoft security update referenced in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45658 as soon as patch details are published; patch available per vendor advisory, but exact fix version is not enumerated in the provided data and must be retrieved from the MSRC page for the affected Windows build. Until the update is deployed, defenders should enable BitLocker pre-boot authentication with a PIN or USB startup key (TPM+PIN) so that a stolen device cannot be unsealed by physical access alone - note this changes the user logon experience and complicates remote/unattended reboots. Additionally, ensure Secure Boot is enabled, disable unnecessary DMA-capable external ports (Thunderbolt/FireWire) via Group Policy or firmware, enable Kernel DMA Protection on supported hardware, and physically secure or remove drives from end-of-life and lost devices; the trade-off of disabling DMA ports is reduced peripheral functionality for users who rely on docking stations and external GPUs.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 33 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 that protects data at rest on Windows systems, typically leveraging a Trusted Platform Module (TPM) to seal the volume master key and release it only when the boot environment is in a known-good state. The CWE-284 (Improper Access Control) classification indicates that an access control or protection mechanism within BitLocker - likely the pre-boot authentication, TPM unsealing flow, or recovery key handling - fails to correctly enforce its security boundary. Because BitLocker relies on the integrity of the boot chain and hardware-rooted secrets, a failure in any link of that chain (e.g., DMA exposure, unsealing logic, or recovery path validation) can allow decrypted access to volumes that should remain sealed.
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:U/C:H/I:H/A:H
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 VectorNVD
Lifecycle Timeline
3DescriptionNVD
Protection mechanism failure in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack.
Executive ViewAI
A security feature bypass in Microsoft Windows BitLocker (CVE-2026-45658, CVSS 7.8) allows attackers with physical access to decrypt protected drives and access sensitive data. No public exploit identified at time of analysis. Organizations relying on BitLocker to protect confidential information on mobile and portable devices face risk of data exposure, particularly if devices are lost, stolen, or accessed by insiders. No vendor patch is currently available.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce strict physical access controls and device supervision protocols; restrict BIOS/firmware access via administrative controls; enable Secure Boot and TPM protections; implement device encryption at storage or hypervisor layer for sensitive data; establish device loss/theft procedures with immediate key revocation; consider temporary BitLocker deactivation on high-risk systems pending patch availability.
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-35572
GHSA-586f-rf9v-97r7
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB