Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain physical access to target device
  2. Delivery
    Connect attack hardware or boot alternate media
  3. Exploit
    Trigger BitLocker protection mechanism failure
  4. Execution
    Mount encrypted volume without credentials
  5. Impact
    Exfiltrate 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Windows Server 2016 10.0.14393.0 <10.0.14393.9339
Windows Server 2022 10.0.20348.0 <10.0.20348.5386
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9339
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2525
Windows Server 2025 10.0.26100.0 <10.0.26100.33158
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9339
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33158
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7548
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7548
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9020
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9020
Windows Server 2019 10.0.17763.0 <10.0.17763.9020
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8875
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8875

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9339
euvd windows_10_version_1809 fix: 10.0.17763.9020
euvd windows_10_version_21h2 fix: 10.0.19044.7548
euvd windows_10_version_22h2 fix: 10.0.19045.7548
euvd windows_11_version_24h2 fix: 10.0.26100.8875
euvd windows_11_version_25h2 fix: 10.0.26200.8875
euvd windows_11_version_26h1 fix: 10.0.28000.2525
euvd windows_server_2016 fix: 10.0.14393.9339
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9339
euvd windows_server_2019 fix: 10.0.17763.9020
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9020
euvd windows_server_2022 fix: 10.0.20348.5386
euvd windows_server_2025 fix: 10.0.26100.33158
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33158

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

Vendor (microsoft) PRIMARY MEDIUM
NVD 4.6 MEDIUM
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 4.6 MEDIUM

Physical access is the sole entry point; no credentials needed; impact is confidentiality-only as encrypted data is exposed but not altered.

3.1 AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorNVD

Attack Vector
Physical
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

3
CVSS changed
Jul 22, 2026 - 15:22 NVD
6.1 (MEDIUM) 4.6 (MEDIUM)
CVE Published
Jul 14, 2026 - 17:08 nvd
MEDIUM 4.6
CVE Published
Jul 14, 2026 - 17:08 cve.org
MEDIUM 6.1

DescriptionNVD

Protection mechanism failure in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack.

Threat Intelligence Overview

EPSS Score
0.4%
Top 70% exploitable
Prevalence
High
BitLocker widely mandated in enterprise Windows fleet management
Vendor Status
Publicly Disclosed:Yes
Exploited:No
Latest Software Release:Exploitation Less Likely
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
High
Technical Impact
Total

Priority Score

43
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +23
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy