Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Gain unsupervised physical device access
  2. Delivery
    Interface with device hardware or firmware layer
  3. Exploit
    Exploit BitLocker protection mechanism failure (CWE-693)
  4. Execution
    Bypass encryption boundary without credentials
  5. Impact
    Read 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.

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

Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23228
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9234
Windows Server 2019 10.0.17763.0 <10.0.17763.8880
Windows Server 2022 10.0.20348.0 <10.0.20348.5256
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 11 Version 24H2 10.0.26100.0 <10.0.26100.8655
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7417
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7417
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26132
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows 11 version 26H1 1.0.0 <10.0.28000.2269
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.32995
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8880
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8655
Windows Server 2016 10.0.14393.0 <10.0.14393.9234
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.8880
Windows Server 2012 6.2.9200.0 <6.2.9200.26132
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7219
Windows Server 2025 10.0.26100.0 <10.0.26100.32995

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
microsoft windows_11_version_26h1_extra_10_0_28000_2269 fix: Windows 11 Version 26H1 for x64-based Systems - extra 10.0.28000.2269
microsoft windows_server_2012_6_2_9200_26132 fix: Windows Server 2012 6.2.9200.26132, Windows Server 2012 (Server Core installation) 6.2.9200.26132
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_32995 fix: Windows Server 2025 10.0.26100.32995, Windows Server 2025 (Server Core installation) 10.0.26100.32995
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 fix: 6.2.9200.26132
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_2012_server_core_installation fix: 6.2.9200.26132
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.32995
euvd windows_server_2025_server_core_installation fix: 10.0.26100.32995

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)
Vendor (microsoft) PRIMARY 5.3 MEDIUM
AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
ENISA EUVD CRITICAL
CIRCL (temporal) 4.6 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
Changed
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Jun 09, 2026 - 19:03 EUVD
CVE Published
Jun 09, 2026 - 17:17 nvd
MEDIUM 5.3

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 77% 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:No
Exploited:No
Latest Software Release:Exploitation Less 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
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
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