Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical device access
-
DeliveryBoot to pre-boot environment
-
ExploitSubmit malformed input to BitLocker
-
ExecutionBypass encryption authentication
-
PersistMount encrypted volumes
-
ImpactExtract sensitive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Attacker requires local access to the Windows system with BitLocker enabled. No authentication or user interaction needed. Affects Windows installations with BitLocker drive encryption active. Remote exploitation not possible; physical or direct local system access mandatory. |
| Impact | Real-world risk assessment requires balancing CVSS severity against practical exploitation constraints. The CVSS 7.7 (High) reflects local attack vector (AV:L), low complexity (AC:L), no privileges required (PR:N), and high confidentiality/integrity impact (C:H/I:H). However, the local attack requirement fundamentally limits exploitation to scenarios involving physical device access, stolen equipment, or malicious insiders with console access. No EPSS data provided, but local-only vulnerabilities historically show lower exploitation rates than remote vectors. No KEV listing indicates no confirmed active exploitation campaigns. The absence of publicly available exploit code further reduces immediate risk. From SSVC perspective: exploitation status is publicly-available-information-only, not active; technical impact is total compromise of encrypted data confidentiality/integrity; automatable is no due to physical access requirement. This creates moderate priority for organizations with physical security controls but becomes critical for portable servers, edge deployments, or environments with insider threat concerns. The security feature bypass nature means compensating controls (physical security, device tracking) become sole protections until patched. |
| Exploit ScenarioDerived | An attacker gains physical access to a BitLocker-encrypted Windows Server 2019 device in a branch office or during equipment transport. By exploiting the input validation flaw during the pre-boot environment or through direct manipulation of boot configuration data, the attacker bypasses BitLocker authentication without requiring TPM PIN, recovery key, or domain credentials. This grants complete access to the encrypted volume contents, allowing extraction of sensitive data, credential databases, or installation of persistent backdoors before returning the device undetected. The low attack complexity (AC:L) indicates exploitation requires only basic technical skills once physical access is achieved. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 14, 2026
BitLocker encryption bypass in Windows Server 2012 through 2022 enables local attackers with physical access to circumvent disk encryption protections without authentication. The vulnerability affects all Server Core and standard editions across ten years of Windows Server releases. Patch available per Microsoft Security Response Center (MSRC-2026-27913). No public exploit identified at time of analysis, but the local attack vector (AV:L) with no authentication requirement (PR:N) indicates high risk in scenarios where physical device access is possible, such as lost/stolen servers or insider threats.
RemediationAI
Apply Microsoft security updates immediately to patch the BitLocker input validation vulnerability. Fixed versions are Windows Server 2012 build 6.2.9200.26026 or later, Windows Server 2012 R2 build 6.3.9600.23132 or later, Windows Server 2016 build 10.0.14393.9060 or later, Windows Server 2019 build 10.0.17763.8644 or later, Windows Server 2022 build 10.0.20348.5020 or later, and Windows Server 2022 23H2 Edition build 10.0.25398.2274 or later. Updates are delivered through standard Windows Update channels or WSUS for enterprise environments. Until patching is complete, implement compensating controls including enhanced physical security for servers with BitLocker-encrypted volumes, restricted physical access to server rooms and data centers, chassis intrusion detection where available, and accelerated decommissioning procedures for devices removed from secure facilities. Review BitLocker recovery key storage security and audit access logs for unauthorized recovery key retrieval attempts. Complete patch deployment guidance available at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-27913.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 16 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-disk encryption technology integrated into Windows Server operating systems to protect data at rest through AES encryption and Trusted Platform Module (TPM) integration. This vulnerability represents an input validation flaw (CWE-20) in the BitLocker security feature itself, where improper validation of locally-provided data allows bypass of encryption protections. The CPE data identifies affected components across Windows Server 2012 (build 6.2.9200), Server 2012 R2 (6.3.9600), Server 2016 (10.0.14393), Server 2019 (10.0.17763), and Server 2022/23H2 (10.0.20348/10.0.25398). Both standard installations and Server Core installations are vulnerable. The input validation weakness likely exists in pre-boot authentication mechanisms, recovery key handling, or volume mounting procedures where BitLocker validates credentials or system state before granting access to encrypted volumes.
Know when Windows Server 2012 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:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Improper input validation in Windows BitLocker allows an unauthorized attacker to bypass a security feature locally.
Executive ViewAI
CVE-2026-27913 is a critical BitLocker bypass affecting Windows Server 2012-2022 that allows attackers with physical device access to decrypt protected disks without authentication, posing significant risk to organizations with sensitive data on servers in vulnerable locations or subject to theft. This vulnerability directly undermines a core security control relied upon by enterprises for data protection at rest and requires immediate patching across all affected server infrastructure. Organizations with servers in shared facilities, remote locations, or facing insider threat risks face elevated exposure.
Apply vendor patch. Interim mitigations pending patch deployment: restrict physical access to affected servers through enhanced facility controls and surveillance; consider air-gapped or isolated storage of servers containing highly sensitive data; implement continuous BitLocker status monitoring and alerts for encryption state changes; evaluate temporary relocation of critical servers to facilities with stronger physical security postures.
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 2012
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
Remote code execution in Microsoft Office 2007-2016 and Windows Vista through 10 allows attackers to execute arbitrary c
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
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
Active Directory Domain Services Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.5), this vulnerabilit
EUVD-2026-22455
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB