Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Obtain local authenticated session
  2. Delivery
    Stage UEFI bypass tooling
  3. Exploit
    Invoke vulnerable Windows UEFI interface
  4. Execution
    Defeat protection mechanism
  5. Persist
    Tamper with boot or firmware trust state
  6. Impact
    Persist 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.

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

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

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
microsoft windows_11_version_26h1_extra_10_0_28000_2269 fix: Windows 11 Version 26H1 for x64-based Systems - extra 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 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

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

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

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

DescriptionCVE.org

Protection mechanism failure in Windows UEFI allows an authorized attacker to bypass a security feature locally.

Executive ViewAI

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.1%
Top 77% 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 Less 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

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
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-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