Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Obtain physical access to device
  2. Delivery
    Interact with boot or hardware interface
  3. Exploit
    Bypass BitLocker protection mechanism
  4. Execution
    Unseal volume master key
  5. Persist
    Read or tamper with encrypted volume
  6. Impact
    Exfiltrate 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.

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

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

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

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_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 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)
NVD PRIMARY 6.8 MEDIUM
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD CRITICAL

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

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

Lifecycle Timeline

3
Severity Changed
Jul 09, 2026 - 00:22 NVD
HIGH MEDIUM
CVSS changed
Jul 09, 2026 - 00:22 NVD
7.8 (HIGH) 6.8 (MEDIUM)
CVE Published
Jun 09, 2026 - 17:17 nvd
HIGH 7.8

DescriptionNVD

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

Executive ViewAI

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.1%
Top 83% 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 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
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
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