Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to target device
-
DeliveryConnect attack hardware or boot alternate media
-
ExploitTrigger BitLocker protection mechanism failure
-
ExecutionMount encrypted volume without credentials
-
ImpactExfiltrate plaintext data from drive
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 access (AV:P) to the target device is the sole hard prerequisite - the attacker must be able to interact directly with the machine. No authentication or existing account privileges are required (PR:N). BitLocker must be enabled on the target volume; devices without BitLocker configured are outside this vulnerability's scope. The most common limiting deployment factor is TPM-only BitLocker without a pre-boot PIN: this configuration does not prompt users for a passphrase at boot, making it the most exploitable posture. Environments using BitLocker with a pre-boot PIN or passphrase add an out-of-band secret that may or may not be circumvented by this specific bypass - this is not clarified in available data. The SSVC determination of Automatable: No confirms that exploitation cannot be scripted at scale across a network, strictly bounding the threat to actors with hands-on physical access. |
| Impact | Real-world risk is substantially constrained by the physical access requirement (AV:P), which eliminates remote or network-based exploitation entirely. EPSS at 0.38% (30th percentile) reflects low observed exploitation probability, and CISA has not added this to KEV. SSVC rates exploitation as none and automatable as no, reinforcing that bulk exploitation is not feasible. However, SSVC Technical Impact is listed as total - likely because a successful bypass exposes the full plaintext contents of a protected drive, which aligns with CVSS C:H. The tension is that while the technical impact on the device is severe (complete confidentiality loss of encrypted data), the attack preconditions (physical possession of the device) limit the realistic threat actor population to insiders, border/customs scenarios, device theft, or nation-state adversaries with physical access capabilities. A publicly available POC on GitHub (referenced in CVE data) meaningfully reduces attacker skill requirements for those who do have physical access. CVSS score of 4.6 (Medium) appropriately reflects this - high consequence but high barrier to exploitation. Priority should be elevated for organizations with high-value laptops in travel or shared-access scenarios. |
| Exploit ScenarioDerived | An attacker steals or temporarily accesses a laptop belonging to a corporate employee - for example, during travel or in an unattended office - and uses the publicly available proof-of-concept (https://gist.github.com/alon710/241fe7f4e9eb231b7e18efd4dc0b5fdd) to bypass BitLocker protections and mount the encrypted drive in a readable state, extracting credentials, intellectual property, or sensitive documents without triggering any authentication prompt or leaving software-visible forensic artifacts. Because the attack requires no authentication (PR:N) and low complexity (AC:L) once physical access is secured, a moderately skilled adversary can complete the exfiltration in minutes using readily available tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 22, 2026
BitLocker encryption bypass on Windows enables an unauthenticated attacker with physical access to circumvent drive-level encryption protections and read confidential data from protected volumes. Affected platforms span Windows 10 (versions 1607 through 22H2), Windows 11 (24H2 through 26H1), and Windows Server 2016 through 2025, with a publicly available proof-of-concept exploit on GitHub lowering the bar for physical-access adversaries. No active exploitation is confirmed (not in CISA KEV; SSVC exploitation status: none), and EPSS sits at 0.38% (30th percentile), consistent with a targeted rather than opportunistic threat; Microsoft has released patches across all affected build lines.
RemediationAI
Apply the Microsoft security update for the relevant Windows build as detailed in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50661. Patched builds confirmed via EUVD are: Windows 10 1607/Server 2016 at 10.0.14393.9339 or later, Windows 10 1809/Server 2019 at 10.0.17763.9020 or later, Windows 10 21H2 at 10.0.19044.7548 or later, Windows 10 22H2 at 10.0.19045.7548 or later, Windows 11 24H2 at 10.0.26100.8875 or later, Windows 11 25H2 at 10.0.26200.8875 or later, Windows 11 26H1 at 10.0.28000.2525 or later, Windows Server 2022 at 10.0.20348.5386 or later, and Windows Server 2025 at 10.0.26100.33158 or later. As compensating controls where immediate patching is not possible, organizations should enforce BitLocker with a pre-boot PIN (rather than TPM-only mode), which adds a second authentication factor that physical attackers cannot bypass without knowing the PIN; trade-off is increased user friction at every boot. Additionally, enabling TPM lockout policies and disabling DMA ports (Thunderbolt/USB4) via firmware or group policy reduces physical attack surface; trade-off is loss of peripheral connectivity. High-value devices in travel scenarios should be placed in monitored device management with remote-wipe capability as a contingency.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 14 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Windows BitLocker is Microsoft's built-in full-disk encryption feature that protects data at rest by encrypting volumes using AES, typically unsealed via a TPM chip, startup PIN, or recovery key. CWE-693 (Protection Mechanism Failure) identifies the root cause class: a defect in the logic or enforcement of the security boundary that BitLocker is designed to enforce, allowing the protection to be bypassed without possessing the correct credentials or recovery material. CPE data confirms the affected surface includes cpe:2.3:a:microsoft:windows_10_version_1607, windows_10_version_1809, windows_10_version_21h2, windows_10_version_22h2, windows_11_version_24h2, windows_11_version_25h2, windows_11_version_26h1, windows_server_2016, windows_server_2019, with EUVD additionally confirming Windows Server 2022 and 2025. The specific bypass mechanism (e.g., cold-boot, DMA attack, pre-boot authentication flaw, TPM sniffing) is not detailed in the available data, but the physical attack vector and no-integrity-impact CVSS profile suggest a read-only data-exfiltration path rather than arbitrary code execution.
Know when Windows Server 2016 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
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Physical access is the sole entry point; no credentials needed; impact is confidentiality-only as encrypted data is exposed but not altered.
Primary rating from Vendor (microsoft).
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
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 Server 2016
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-44122
GHSA-6grp-7qp6-c6r9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB