Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Gain physical device access
  2. Delivery
    Boot to pre-boot environment
  3. Exploit
    Submit malformed input to BitLocker
  4. Execution
    Bypass encryption authentication
  5. Persist
    Mount encrypted volumes
  6. Impact
    Extract 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.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 – 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

Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23132
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8644
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23132
Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.0 <10.0.25398.2274
Windows Server 2019 10.0.17763.0 <10.0.17763.8644
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9060
Windows Server 2016 10.0.14393.0 <10.0.14393.9060
Windows Server 2012 6.2.9200.0 <6.2.9200.26026
Windows Server 2022 10.0.20348.0 <10.0.20348.5020
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26026

Affected Packages

microsoft windows_server_2012_6_2_9200_26026 fix: Windows Server 2012 6.2.9200.26026, Windows Server 2012 (Server Core installation) 6.2.9200.26026
microsoft windows_server_2012_r2_6_3_9600_23132 fix: Windows Server 2012 R2 6.3.9600.23132, Windows Server 2012 R2 (Server Core installation) 6.3.9600.23132
microsoft windows_server_2016_10_0_14393_9060 fix: Windows Server 2016 10.0.14393.9060, Windows Server 2016 (Server Core installation) 10.0.14393.9060
microsoft windows_server_2019_10_0_17763_8644 fix: Windows Server 2019 10.0.17763.8644, Windows Server 2019 (Server Core installation) 10.0.17763.8644
microsoft windows_server_2022_10_0_20348_5020 fix: Windows Server 2022 10.0.20348.5020, Windows Server 2022 (Server Core installation) 10.0.20348.5020
microsoft windows_server_2022_23h2_edition_10_0_25398_2274 fix: Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.2274
euvd windows_server_2012 fix: 6.2.9200.26026
euvd windows_server_2012_r2 fix: 6.3.9600.23132
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23132
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26026
euvd windows_server_2016 fix: 10.0.14393.9060
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9060
euvd windows_server_2019 fix: 10.0.17763.8644
euvd windows_server_2019_server_core_installation fix: 10.0.17763.8644
euvd windows_server_2022 fix: 10.0.20348.5020
euvd windows_server_2022_23h2_edition_server_core_installation fix: 10.0.25398.2274

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

Vendor (microsoft) PRIMARY 7.7 HIGH
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CIRCL (temporal) 6.7 MEDIUM

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

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

Lifecycle Timeline

2
Patch released
Apr 14, 2026 - 17:46 nvd
Patch available
CVE Published
Apr 14, 2026 - 16:58 nvd
HIGH 7.7

DescriptionCVE.org

Improper input validation in Windows BitLocker allows an unauthorized attacker to bypass a security feature locally.

Executive ViewAI

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.1%
Top 80% exploitable
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
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 HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
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-2017-0199 HIGH POC
7.8 Apr 12

Remote code execution in Microsoft Office 2007-2016 and Windows Vista through 10 allows attackers to execute arbitrary c

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

CVE-2021-42278 HIGH POC
7.5 Nov 10

Active Directory Domain Services Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.5), this vulnerabilit

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