Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to unattended device
-
DeliveryReboot or power-cycle hardware
-
ExploitTrigger Boot Manager protection mechanism failure via crafted input or media
-
ExecutionLoad unsigned or unauthorized pre-OS code
-
PersistExecute arbitrary code before Windows OS integrity checks
-
ImpactEscalate to full system control and persist bootkit or exfiltrate protected data
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 access to the target device is the mandatory and sole prerequisite - CVSS AV:P confirms remote exploitation is categorically impossible. The attacker must be able to interact with device hardware directly, such as attaching USB boot media, pressing power/reset controls, or manipulating UEFI firmware settings. No prior system authentication or user-level privileges are required (PR:N, UI:N). The following factors limit exploitation: the attacker must be physically present; full-disk encryption with pre-boot PIN (BitLocker TPM+PIN) substantially increases difficulty; disabled external boot device ordering in UEFI raises the bar further; and physical security controls such as locked facilities and device cable locks eliminate the attack surface entirely for secured assets. There is no configuration of the Windows Boot Manager that exposes this vulnerability to remote or network-based exploitation. |
| Impact | The physical attack vector (AV:P) is the primary limiting factor and significantly constrains real-world exploitability - an attacker must have hands-on access to target hardware, which prevents mass remote exploitation. Despite a CVSS base score of 6.8, the C:H/I:H/A:H impact triad reflects severe consequences if that physical bar is cleared: full pre-OS compromise with access to disk encryption keys, persistent bootkit implantation, and complete system integrity loss. This threat profile maps to supply-chain interception, insider attacks, border crossing device inspection, theft-based exfiltration, and Evil Maid scenarios against unattended devices. EPSS data is not provided in the available intelligence; physical-vector flaws typically score low on automated exploitation probability metrics due to the inherent automation barrier. No KEV listing is recorded, and no public exploit code has been identified at time of analysis. The breadth of affected Windows versions - from Server 2012 through the latest Windows 11 and Server 2025 builds - combined with the ubiquitous deployment footprint of Windows means the aggregate attack surface is enormous even if individual exploitation requires physical presence. Organizations managing high-value mobile device fleets in executive, diplomatic, law enforcement, or defense contexts face realistic physical-access threat models and should prioritize patching. |
| Exploit ScenarioDerived | An attacker with physical access to an unattended Windows laptop - during a hotel-room Evil Maid scenario, brief office intrusion, or border crossing device inspection - reboots the system and exploits the Boot Manager protection mechanism failure, either via crafted external boot media or UEFI variable manipulation, to bypass Secure Boot and load unauthorized pre-OS code. Execution at this stage grants the attacker full control prior to OS integrity checks, enabling extraction of BitLocker volume master keys from memory, installation of a persistent bootkit, or complete reimaging of the device. No public exploit code has been identified at time of analysis; exploitation at this sophistication level is realistic for nation-state and targeted espionage threat actors. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Privilege escalation in Windows Boot Manager allows an unauthorized attacker with physical access to achieve full pre-OS system compromise, yielding high confidentiality, integrity, and availability impact across a sweeping range of Windows desktop and server editions. The root cause is a protection mechanism failure (CWE-693) in the boot-time security stack - consistent with a Secure Boot or early-launch integrity bypass - that an adversary can exploit without any prior authentication or system privileges once physical access is obtained. Microsoft has released patches for all affected versions; no public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
RemediationAI
Apply the Microsoft-released patches for each affected Windows version as detailed in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-77892; target build numbers are enumerated in the EUVD version data (e.g., Windows 11 23H2 to 10.0.22631.7582, Windows Server 2025 to 10.0.26100.33438, Windows 10 22H2 to 10.0.19045.7725). For organizations that cannot immediately patch - notably Windows Server 2012 and 2012 R2 which are beyond mainstream support - compensating controls include enforcing BitLocker with TPM+PIN pre-boot authentication (raising the exploitation bar by requiring attacker knowledge of the PIN beyond physical presence), disabling boot from external media in UEFI firmware settings (trade-off: complicates recovery scenarios), enabling UEFI Secure Boot with a hardened custom key policy, and maintaining strict physical device security controls such as cable locks and secure storage when devices are unattended. Note that Boot Manager protection mechanism flaws may additionally require Microsoft to issue updated Secure Boot DBX revocations to prevent rollback attacks using older vulnerable boot binaries - verify that the UEFI firmware and Secure Boot forbidden-signature database are also updated per advisory guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 19 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Windows Boot Manager is the UEFI/BIOS-stage component responsible for loading the Windows OS and enforcing boot-time security controls including Secure Boot policy and early-launch antimalware (ELAM). CWE-693 (Protection Mechanism Failure) indicates that a security enforcement mechanism within this stage can be circumvented, allowing execution of untrusted or unauthorized boot code. This class of flaw is historically associated with Secure Boot bypass techniques - crafted boot media, UEFI variable manipulation, or exploitation of signed-but-vulnerable Boot Manager binaries that Microsoft must subsequently revoke via DBX (Forbidden Signatures Database) updates. The affected build ranges span Windows 10 (builds 14393 through 22631), Windows 11 (22631 through 28000/26200), and Windows Server from 6.2.9200 (Server 2012) through 10.0.26100 (Server 2025), indicating a broad architectural deficiency rather than a narrow version-specific regression. The CVSS physical attack vector (AV:P) is authoritative - this vulnerability cannot be triggered remotely under any network configuration.
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
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Physical-only vector confirmed by description; no prior privileges required; full CIA impact consistent with pre-OS arbitrary code execution gaining complete device control.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
No cwe for this issue in Windows Boot Manager allows an unauthorized attacker to elevate privileges with a physical attack.
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 10 1607
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
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
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
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
EUVD-2026-73281
GHSA-7vcg-9vhw-ghh3
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB