CVE-2026-45585
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
BitLocker bypass in Windows Recovery Environment on Windows 11/Server 2022/2025 allows arbitrary shell access via crafted FsTx folder.
Vulnerability
The vulnerability is a security feature bypass in the Windows Recovery Environment (WinRE) component, publicly referred to as "YellowKey". It allows an attacker to execute arbitrary commands on a BitLocker-protected system by placing a specially crafted FsTx folder in the System Volume Information directory of an external USB drive or the EFI partition. The bug is present in Windows 11, Server 2022, and Server 2025; Windows 10 is not affected [1]. The FsTx folder in WinRE contains functionality that triggers the bypass, while the same folder name exists in normal Windows installations without this behavior [1].
Exploitation
An attacker with physical access to the target device can reproduce the exploit by copying the FsTx folder (available in the proof-of-concept repository) to a USB stick formatted with NTFS, FAT32, or exFAT, inside YourUSBStick:\System Volume Information\FsTx. Alternatively, the folder can be placed directly on the EFI partition if the disk is removed and reinserted. The attacker then reboots the system into WinRE by holding SHIFT and clicking Restart. Upon reboot, the attacker must press and hold CTRL; this action spawns a shell with unrestricted access to the BitLocker-encrypted volume [1].
Impact
Upon successful exploitation, the attacker gains a shell with full read and write access to data on the BitLocker-protected volume, bypassing the encryption authentication. This results in a complete compromise of confidentiality and integrity of the protected data, without needing the BitLocker recovery key or user credentials [1].
Mitigation
As of the publication date (2026-05-20), Microsoft has acknowledged the vulnerability and stated that a security update is forthcoming, but no patch has been released. No specific workarounds are provided in the available references. Administrators should monitor Microsoft Security Response Center for updates and consider restricting physical access to devices or disabling WinRE if feasible until the patch is applied [1].
AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
1- msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585nvdVendor AdvisoryMitigation
News mentions
4- Microsoft Rolls Out Mitigations for ‘YellowKey’ BitLocker BypassSecurityWeek · May 20, 2026
- Microsoft provides mitigation for “YellowKey” BitLocker bypass flaw (CVE-2026-45585)Help Net Security · May 20, 2026
- Microsoft Releases Mitigation for YellowKey BitLocker Bypass CVE-2026-45585 ExploitThe Hacker News · May 20, 2026
- Microsoft shares mitigation for YellowKey Windows zero-dayBleepingComputer · May 20, 2026