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
    Trigger BitLocker protection mechanism failure (CWE-306)
  3. Exploit
    Bypass pre-boot authentication gate
  4. Execution
    Mount and access plaintext encrypted volume
  5. Impact
    Exfiltrate sensitive data or implant persistent malware

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Physical presence at the target device is the firm prerequisite for exploitation, confirmed by CVSS vector AV:P - remote exploitation is not possible under any configuration. No privileges are required (PR:N) and no user interaction is needed (UI:N), meaning the device does not need to be powered on, logged in, or attended by the owner at the time of attack. The specific BitLocker configuration mode or Windows feature flag that triggers the protection mechanism failure (CWE-306) is not enumerated in the available description; the MSRC advisory should be consulted to determine whether only TPM-only configurations, specific Windows editions, or particular boot modes are susceptible. Exploitation is bounded by: (1) the physical access requirement limiting attackers to those who can physically handle the device, (2) the need to target Windows systems with BitLocker enabled and the affected version installed, and (3) any device-level protections such as Secure Boot or BIOS passwords that may independently raise attacker prerequisites beyond what this CVE alone describes.

Impact

The CVSS 6.8 Medium score is appropriate given the physical access requirement (AV:P), which substantially narrows the attacker population to individuals who can physically handle the target device - such as in theft, loss-of-device, or insider threat scenarios. However, the H/H/H impact triad (confidentiality, integrity, availability all High) signals that once the physical threshold is crossed, the exploitation is unconstrained: the attacker gains full data exposure and write access. Attack complexity is low (AC:L) and no privileges or user interaction are required (PR:N, UI:N), meaning physical access alone is sufficient for a technically capable adversary. No EPSS data was provided, preventing probabilistic exploitation likelihood assessment. The vulnerability is not listed in the CISA KEV catalog based on available data, suggesting no confirmed widespread active exploitation at time of analysis. For organizations relying on BitLocker as the primary data-at-rest control for mobile workforces - laptops, tablets, field devices - this represents a meaningful real-world risk despite the medium CVSS score, as device theft is a common event. The absence of POC and KEV listing means this is currently a targeted-exposure risk rather than an opportunistic mass-exploitation threat.

Exploit ScenarioDerived

An attacker steals or gains unsupervised physical access to a Windows laptop protected by BitLocker - for example, left unattended in a conference room or seized at a border crossing - and exploits the missing authentication enforcement (CWE-306) to interact directly with the encrypted drive and bypass BitLocker's protection gate without supplying a PIN or recovery key. With the encryption barrier removed, the attacker mounts the volume and accesses plaintext files, credentials, or configuration data, or plants persistent malware in the now-writable system partition. No public exploit code has been identified at time of analysis, but the low attack complexity (AC:L) in the CVSS vector indicates that exploitation does not require specialized tools or chained vulnerabilities once physical access is established.

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

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

Alert me

AnalysisAIv1 – Jun 09, 2026

BitLocker's protection mechanism on Windows fails to enforce a critical authentication or verification step, permitting a physically present attacker to bypass full-disk encryption without credentials, a recovery key, or elevated privileges. Despite a CVSS score of 6.8 (Medium) - moderated by the physical access requirement - the impact ratings are High across confidentiality, integrity, and availability, meaning successful exploitation grants complete access to encrypted data and the underlying system. No public exploit has been identified at time of analysis, and Microsoft has released a patch via the MSRC update guide.

RemediationAI

Microsoft has released a patch addressing CVE-2026-50507; the exact patched Windows version is not independently confirmed from the available data beyond 'patch available from vendor,' so administrators should consult the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50507 for the specific KB article and affected build numbers, then apply the relevant cumulative or security update through Windows Update, WSUS, or SCCM. As compensating controls prior to patching or for defense-in-depth, organizations should enforce BitLocker with a pre-boot PIN or startup key in addition to TPM (rather than TPM-only mode), as this raises the bar for physical attackers - note this adds user friction at every boot cycle. Disabling USB and external boot options in BIOS/UEFI firmware and setting a BIOS/UEFI password prevents attackers from booting alternative OS environments to bypass BitLocker. For high-value or high-mobility devices, enabling Microsoft Entra ID or on-premises remote wipe capabilities ensures data can be rendered inaccessible if a device is confirmed stolen. Physical security controls such as device tracking and cable locks provide additional deterrence against the physical access prerequisite.

Affected VersionsENISA

Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7219
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9234
Windows Server 2025 10.0.26100.0 <10.0.26100.8655
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8655
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.8655
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8880
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23228
Windows Server 2016 10.0.14393.0 <10.0.14393.9234
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7417
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7417
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9234
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23228
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.8880
Windows Server 2022 10.0.20348.0 <10.0.20348.5256
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8655
Windows Server 2019 10.0.17763.0 <10.0.17763.8880

Affected Packages

microsoft windows_10_version_1607_10_0_14393_9234 fix: Windows 10 Version 1607 for 32-bit Systems 10.0.14393.9234, Windows 10 Version 1607 for x64-based Systems 10.0.14393.9234
microsoft windows_10_version_1809_10_0_17763_8880 fix: Windows 10 Version 1809 for 32-bit Systems 10.0.17763.8880, Windows 10 Version 1809 for x64-based Systems 10.0.17763.8880
microsoft windows_10_version_21h2_10_0_19044_7417 fix: Windows 10 Version 21H2 for 32-bit Systems 10.0.19044.7417, Windows 10 Version 21H2 for ARM64-based Systems 10.0.19044.7417, Windows 10 Version 21H2 for x64-based Systems 10.0.19044.7417
microsoft windows_10_version_22h2_10_0_19045_7417 fix: Windows 10 Version 22H2 for 32-bit Systems 10.0.19045.7417, Windows 10 Version 22H2 for ARM64-based Systems 10.0.19045.7417, Windows 10 Version 22H2 for x64-based Systems 10.0.19045.7417
microsoft windows_11_version_23h2_10_0_22631_7219 fix: Windows 11 Version 23H2 for ARM64-based Systems 10.0.22631.7219, Windows 11 Version 23H2 for x64-based Systems 10.0.22631.7219
microsoft windows_11_version_24h2_10_0_26100_8655 fix: Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.8655, Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8655
microsoft windows_11_version_25h2_10_0_26200_8655 fix: Windows 11 Version 25H2 for ARM64-based Systems 10.0.26200.8655, Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8655
microsoft windows_11_version_26h1_10_0_28000_2269 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2269, Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269
microsoft windows_server_2012_r2_6_3_9600_23228 fix: Windows Server 2012 R2 6.3.9600.23228, Windows Server 2012 R2 (Server Core installation) 6.3.9600.23228
microsoft windows_server_2016_10_0_14393_9234 fix: Windows Server 2016 10.0.14393.9234, Windows Server 2016 (Server Core installation) 10.0.14393.9234
microsoft windows_server_2019_10_0_17763_8880 fix: Windows Server 2019 10.0.17763.8880, Windows Server 2019 (Server Core installation) 10.0.17763.8880
microsoft windows_server_2022_10_0_20348_5256 fix: Windows Server 2022 10.0.20348.5256, Windows Server 2022 (Server Core installation) 10.0.20348.5256
microsoft windows_server_2025_10_0_26100_8655 fix: Windows Server 2025 10.0.26100.8655, Windows Server 2025 (Server Core installation) 10.0.26100.8655
euvd windows_10_version_1607 fix: 10.0.14393.9234
euvd windows_10_version_1809 fix: 10.0.17763.8880
euvd windows_10_version_21h2 fix: 10.0.19044.7417
euvd windows_10_version_22h2 fix: 10.0.19045.7417
euvd windows_11_version_23h2 fix: 10.0.22631.7219
euvd windows_11_version_24h2 fix: 10.0.26100.8655
euvd windows_11_version_25h2 fix: 10.0.26200.8655
euvd windows_11_version_26h1 fix: 10.0.28000.2269
euvd windows_server_2012_r2 fix: 6.3.9600.23228
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23228
euvd windows_server_2016 fix: 10.0.14393.9234
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9234
euvd windows_server_2019 fix: 10.0.17763.8880
euvd windows_server_2019_server_core_installation fix: 10.0.17763.8880
euvd windows_server_2022 fix: 10.0.20348.5256
euvd windows_server_2025 fix: 10.0.26100.8655
euvd windows_server_2025_server_core_installation fix: 10.0.26100.8655

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 30 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

Windows BitLocker is Microsoft's built-in full-volume encryption technology, designed to protect data at rest on Windows devices by encrypting the entire drive and requiring authentication (TPM, PIN, recovery key, or combination) to unlock it at boot. CWE-306 (Missing Authentication for Critical Function) identifies the root cause class: a critical security gate - specifically the protection mechanism enforcing BitLocker's access controls - is missing or bypassable, allowing an unauthorized actor to circumvent encryption without supplying the required authentication factor. This CWE commonly manifests in BitLocker contexts as inadequate enforcement of pre-boot PIN requirements, exploitable TPM-only unlock paths, or boot-sequence verification steps that can be skipped through physical manipulation (e.g., cold-boot attacks, DMA attacks, or firmware-level bypasses). The CVSS vector AV:P confirms that exploitation requires direct physical presence at the device.

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)
Vendor (microsoft) PRIMARY 6.8 MEDIUM
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD CRITICAL
CIRCL (temporal) 6.1 MEDIUM

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

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

DescriptionCVE.org

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.1%
Top 73% exploitable
EU Gov Alert
Listed
Top-tier national CERT alert
Threat Intel
1
1 sources
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:Yes
Exploited:No
Latest Software Release:Exploitation More Likely
Data Quality
7 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 No
EPSS 0.1%
Patch available Yes
Active threat Yes
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
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

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

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