Skip to main content

Microsoft Windows EUVDEUVD-2026-31006

| CVE-2026-45585 MEDIUM
Command Injection (CWE-77)
2026-05-20 secure@microsoft.com GHSA-2h24-8rjh-qgjv
6.8
CVSS 3.1 · Vendor: microsoft
Temporal: 6.3
View

Attack ChainAIDerived

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

  1. Access
    Gain physical access to unattended Windows device
  2. Delivery
    Access exposed pre-boot or locked-state interface
  3. Exploit
    Inject OS commands via YellowKey technique (CWE-77)
  4. Execution
    Bypass Windows security feature enforcement
  5. Impact
    Achieve full confidentiality, integrity, and availability compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Command injection prevention
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Physical access to the target Windows device is the mandatory prerequisite - the CVSS AV:P vector explicitly rules out remote or adjacent-network exploitation. Once physical presence is established, no authentication or prior privileges are required (PR:N), and no victim interaction is needed (UI:N), making the attack entirely attacker-driven. The specific Windows component, interface, or configuration state that must be reachable for injection (e.g., recovery console, pre-boot diagnostics, locked screen shell) is not named in available data and should be confirmed via the MSRC advisory. The primary limiting factor is physical proximity - this vulnerability cannot be exploited over a network, over Bluetooth, or remotely in any confirmed form based on the AV:P vector. Attack complexity is low (AC:L) once access is achieved, meaning no race conditions, special timing, or environmental prerequisites are required beyond physical presence.

Impact

CVSS 6.8 (Medium) reflects the physical access prerequisite dragging down an otherwise total-impact vulnerability. The C:H/I:H/A:H triad across an unchanged scope means successful exploitation yields full device compromise, but AV:P is the dominant risk-limiting signal - remote exploitation is ruled out by the vector. EPSS data is not available in the provided intelligence, so exploitation probability cannot be quantified by that framework. KEV status: not listed in CISA KEV at time of analysis, meaning confirmed widespread active exploitation has not been formally reported. However, a public POC exists per Microsoft's own advisory, which is a meaningful escalation - any attacker with physical access can now reproduce the attack without deep expertise. SSVC signals: exploitation possible (POC public), automatable at scale is unlikely (physical vector), technical impact is total. Real-world priority is high for organizations managing high-value physical assets - executive laptops, government endpoints, kiosks, shared terminals, border-crossing or customs devices - and substantially lower for organizations with strong physical access controls and no shared-device risk. The gap between CVSS 6.8 and the C:H/I:H/A:H impact ratings warrants attention: do not dismiss this as medium risk for physically exposed deployments.

Exploit ScenarioDerived

An adversary with brief physical access to a target Windows device - such as an unattended laptop at a conference, a shared workstation in a semi-public office, or a kiosk in a retail or government facility - accesses an exposed pre-boot or locked-state interface and injects commands using the publicly available 'YellowKey' POC. With no authentication required and low attack complexity, the injected commands bypass the Windows security feature protecting that interface, granting the attacker full control of the device including access to encrypted volumes, credential stores, or the ability to install persistent implants before the legitimate user returns.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 20, 2026

Windows security feature bypass, publicly dubbed 'YellowKey', exposes systems to full confidentiality, integrity, and availability compromise via command injection (CWE-77) requiring only physical access - no credentials or user interaction needed. A proof-of-concept was released publicly prior to patch availability, violating coordinated disclosure norms, which lowers the attacker skill bar significantly. No vendor-released patch exists at time of analysis; Microsoft has confirmed the issue and is preparing a security update.

RemediationAI

No vendor-released patch is available at time of analysis - Microsoft's advisory language explicitly states mitigation guidance is being issued 'until the security update is made available.' Monitor https://msrc.apple.com/update-guide/vulnerability/CVE-2026-45585 and Microsoft's Patch Tuesday release cycle for the forthcoming fix, and apply it immediately upon release. In the interim, enforce strict physical access controls as the primary compensating measure: restrict physical access to Windows endpoints to authorized personnel only, and treat unattended device scenarios (hotels, open offices, shared kiosks) as elevated risk. Enable BitLocker with a pre-boot PIN (not TPM-only) to require a secret for device access before Windows loads, limiting attack surface on the interface likely targeted by YellowKey - trade-off is user friction at boot. Configure BIOS/UEFI with an administrator password and disable booting from external media to prevent circumvention via live OS. Enable Secure Boot and verify TPM-based attestation is active. For shared or kiosk Windows deployments, evaluate whether devices can be physically secured (cable locks, locked enclosures) or temporarily taken offline until the patch is available. Do not rely on software-layer mitigations alone given the physical-access attack vector.

Affected VersionsENISA

Windows Server 2025 (Server Core installation) - (version not specified)
Windows 11 Version 24H2 - (version not specified)
Windows 11 Version 25H2 - (version not specified)
Windows Server 2025 - (version not specified)
Windows 11 version 26H1 - (version not specified)

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-77 (Improper Neutralization of Special Elements used in a Command) indicates that some Windows interface - likely a pre-boot environment, locked-screen shell, recovery console, or accessible diagnostic utility - fails to sanitize special characters, allowing injected OS commands to execute with elevated or system-level privilege. The CVSS vector AV:P (Physical) confirms exploitation requires hands-on access to the hardware, while PR:N and AC:L indicate no credentials are needed and the injection point is trivially reachable once physical presence is established. The 'security feature bypass' classification suggests the command injection is used to circumvent a protective mechanism such as Secure Boot enforcement, Windows Defender credential guard, disk encryption lock, or a kiosk-mode restriction, rather than being a standalone RCE class on a normally running system. Affected CPE strings are not enumerated in the available intelligence; consult the MSRC advisory for exact product and version scoping.

Know when Windows 11 24h2 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 6.8 MEDIUM
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CIRCL (temporal) 6.3 MEDIUM

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

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

DescriptionCVE.org

Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as "YellowKey". The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices. We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available.

Threat Intelligence Overview

EPSS Score
0.1%
Top 76% exploitable
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:Yes
Exploited:No
Latest Software Release:Exploitation More Likely
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment MSRC GitHub VulDB

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 MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

54
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2013-3900 MEDIUM
5.5 Dec 11

Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update

CVE-2025-21293 HIGH POC
8.8 Jan 14

Active Directory Domain Services contains an elevation of privilege vulnerability that allows authenticated domain users

CVE-2024-43461 HIGH
8.8 Sep 10

Windows MSHTML Platform Spoofing Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitab

CVE-2025-30397 HIGH POC
7.5 May 13

Microsoft Scripting Engine contains a type confusion vulnerability allowing unauthorized remote code execution over the

CVE-2024-49039 HIGH POC
8.8 Nov 12

Windows Task Scheduler Elevation of Privilege Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is low a

CVE-2026-96951 HIGH POC
8.8 Oct 13

Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then

CVE-2026-81963 HIGH POC
7.8 Sep 08

Symlink following (CWE-59) in the Windows Update Stack enables a locally authenticated attacker with standard user privi

CVE-2025-26633 HIGH POC
7.0 Mar 11

A security feature bypass in Microsoft Management Console (MMC) allows attackers to evade security warnings and execute

CVE-2026-68820 HIGH POC
7.0 Aug 11

Privilege escalation in the Windows Ancillary Function Driver for WinSock (afd.sys) allows a locally authenticated attac

CVE-2025-32706 HIGH POC
7.8 May 13

Windows CLFS Driver contains an input validation flaw enabling local privilege escalation, yet another CLFS kernel vulne

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