Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local authenticated session
-
DeliveryStage UEFI bypass tooling
-
ExploitInvoke vulnerable Windows UEFI interface
-
ExecutionDefeat protection mechanism
-
PersistTamper with boot or firmware trust state
-
ImpactPersist across reboots with elevated trust
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 | Exploitation requires local code execution on the target Windows host as an authenticated user with low privileges (CVSS PR:L), with no user interaction needed (UI:N) and no network reachability (AV:L), meaning the attacker must already be on the system via prior compromise, malicious insider access, or physical/console access. Limiting factors include the requirement for a valid local logon session on a Windows build that ships the vulnerable UEFI component, and the bypass targets a specific (unnamed in the provided description) Windows UEFI security feature - systems where that feature is not enabled or not relied upon for the defender's threat model gain little additional risk, while systems depending on UEFI-backed boot integrity (Secure Boot, VBS, BitLocker measured boot) are the meaningful targets. |
| Impact | The CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H yields a base score of 7.8 and characterizes this as a local attack requiring low privileges and no user interaction, with high impact across CIA - consistent with a privileged-user-to-firmware-trust bypass rather than a remote compromise. No EPSS score, KEV listing, SSVC decision, or POC indicator was supplied, so probabilistic exploitation likelihood cannot be quantified from the provided data; however, the local-only attack vector and required prior code execution as an authenticated user materially lower real-world risk versus a network-reachable RCE of the same score. The signals are not in conflict but are sparse: a single Microsoft advisory reference is provided, and the description's terse 'bypass a security feature' wording does not name which protection (e.g., Secure Boot, HVCI, VBS) is defeated, which limits ability to prioritize against specific threat models - verify with the MSRC advisory before treating this as a boot-chain compromise versus a lower-tier feature bypass. |
| Exploit ScenarioDerived | An attacker who has already obtained a standard authenticated local session on a Windows endpoint - for example via phishing-delivered malware or stolen credentials - executes a crafted tool that interacts with the vulnerable UEFI security mechanism to disable or bypass it, then leverages that bypass to tamper with boot components, escalate trust, or persist across reboots. No public exploit identified at time of analysis, and the local-only AV:L vector means this would typically be chained after an initial foothold rather than used for initial access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 09, 2026
Security feature bypass in Windows UEFI allows an authenticated local attacker with low privileges to circumvent a protection mechanism, resulting in high confidentiality, integrity, and availability impact on the host. The flaw is rooted in CWE-693 (Protection Mechanism Failure) within the Windows UEFI firmware layer, and Microsoft (secure@microsoft.com) is the reporting CNA. No public exploit identified at time of analysis, and the issue is not currently listed in CISA KEV.
RemediationAI
Apply the Microsoft security update referenced in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45656 as soon as it is published for your Windows edition; patch available per vendor advisory, though no specific fixed build number is provided in the input data, so consult that advisory for the exact KB and any firmware/UEFI capsule updates that must accompany the OS patch. As compensating controls while patching is staged, restrict local interactive and administrative access on affected hosts since exploitation requires PR:L local privileges (trade-off: tighter local admin controls may impede support workflows), enable and monitor Secure Boot and measured boot attestation via tools such as Microsoft Defender for Endpoint or Azure Attestation to detect bypass attempts (trade-off: attestation will flag legitimate firmware changes), and keep BitLocker enabled with TPM+PIN where feasible so that a firmware-level security bypass does not trivially lead to offline data exposure (trade-off: TPM+PIN adds boot friction for end users).
Affected VersionsENISA
Affected Packages
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
UEFI (Unified Extensible Firmware Interface) is the pre-boot firmware environment that initializes hardware and hands control to the operating system loader; on Windows systems it underpins Secure Boot, BitLocker measurement, and the early boot trust chain. CWE-693 (Protection Mechanism Failure) indicates that an existing security control in the UEFI implementation is bypassed or rendered ineffective rather than missing entirely - typical examples in this class include flaws that defeat Secure Boot, variable write protection, SMM lockdown, or Boot Guard. No CPE strings were provided in the input, so the exact affected Windows builds and firmware components must be confirmed via the Microsoft Security Update Guide entry referenced by NVD.
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
DescriptionCVE.org
Protection mechanism failure in Windows UEFI allows an authorized attacker to bypass a security feature locally.
Executive ViewAI
Windows UEFI firmware contains a protection mechanism bypass (CVE-2026-45656, CVSS 7.8) enabling authenticated local users to circumvent security controls with potential impact to system confidentiality, integrity, and availability. This firmware-layer vulnerability poses organizational risk because compromise persists across operating system reimaging and standard recovery procedures. Microsoft has not released a patch; immediate access restriction and enhanced monitoring are required.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce principle of least privilege for local accounts; enable UEFI Secure Boot and firmware access controls; implement system monitoring for unauthorized privilege escalation and firmware access attempts; restrict physical access to affected systems; isolate critical systems on separate network segments; document firmware baselines for anomaly detection.
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-35696
GHSA-44jf-fmcv-xp6f
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB