Microsoft Releases Mitigation for YellowKey BitLocker Bypass CVE-2026-45585 Exploit
The Hacker NewsArchived May 20, 2026✓ Full text saved
Microsoft on Tuesday released a mitigation for a BitLocker bypass vulnerability named YellowKey following its public disclosure last week. The zero-day flaw, now tracked as CVE-2026-45585, carries a CVSS score of 6.8. It has been described as a BitLocker security feature bypass. "Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as 'YellowKey,'" the
Full text archived locally
✦ AI Summary· Claude Sonnet
Microsoft Releases Mitigation for YellowKey BitLocker Bypass CVE-2026-45585 Exploit
Ravie LakshmananMay 20, 2026Vulnerability / Encryption
Microsoft on Tuesday released a mitigation for a BitLocker bypass vulnerability named YellowKey following its public disclosure last week.
The zero-day flaw, now tracked as CVE-2026-45585, carries a CVSS score of 6.8. It has been described as a BitLocker security feature bypass.
"Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as 'YellowKey,'" the tech giant said in an advisory. "The proof of concept for this vulnerability has been made public, violating coordinated vulnerability best practices."
The issue impacts Windows 11 version 26H1 for x64-based Systems, Windows 11 Version 24H2 for x64-based Systems, Windows 11 Version 25H2 for x64-based Systems, Windows Server 2025, and Windows Server 2025 (Server Core installation).
YellowKey was disclosed by a security researcher named Chaotic Eclipse (aka Nightmare-Eclipse). It essentially involves placing specially crafted 'FsTx' files on a USB drive or EFI partition, plugging the USB drive into the target Windows computer with BitLocker protections turned on, rebooting into the Windows Recovery Environment (WinRE), and triggering a shell with unrestricted access by holding down the CTRL key.
"If you did everything properly, a shell will spawn with unrestricted access to the BitLocker protected volume," the researcher noted in a GitHub post.
Redmond noted that successful exploitation could permit an attacker with physical access to sidestep the BitLocker Device Encryption feature on the system storage device and gain access to encrypted data.
"To break encryption, YellowKey abuses a behavioral trust assumption in the recovery interface, allowing attackers to spawn an unrestricted shell with full access to the encrypted volume during the pre-boot recovery sequence," LevelBlue said. "And because YellowKey doesn't require software installation, existing credentials, or network access to break encryption, any machine that has a USB port and can be rebooted can be a target."
To address the risk, the following mitigations have been outlined:
Mount the WinRE image on each device.
Mount the system registry hive of the mounted WinRE image.
Modify BootExecute by removing "autofstx.exe" value from Session Manager's BootExecute REG_MULTI_SZ value.
Save and unload Registry hive.
Unmount and commit the updated WinRE image.
Reestablish BitLocker trust for WinRE.
"Specifically, you prevent the FsTx Auto Recovery Utility, autofstx.exe, from automatically starting when the WinRE image launches," security researcher Will Dormann said. "With this change, the Transactional NTFS replaying that deletes winpeshl.ini no longer happens. It also recommends switching from TPM-only to TPM+PIN."
Microsoft also emphasized that users can be safeguarded against exploitation by configuring BitLocker on already encrypted devices with "TPM-only" protector by switching to "TPM+PIN" mode via PowerShell, the command line, or the control panel. This will require a PIN to decrypt the drive at startup, effectively backing YellowKey attacks.
On devices that are not encrypted, administrators are advised to enable the "Require additional authentication at startup" option via Microsoft Intune or Group Policies and ensure that "Configure TPM startup PIN" is set to "Require startup PIN with TPM."
Found this article interesting? Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post.
SHARE
Tweet
Share
Share
SHARE
BitLocker, cybersecurity, encryption, Microsoft, Vulnerability, Windows, Zero-Day
⚡ Top Stories This Week
On-Prem Microsoft Exchange Server CVE-2026-42897 Exploited via Crafted Email
Mini Shai-Hulud Worm Compromises TanStack, Mistral AI, Guardrails AI and More Packages
Hackers Used AI to Develop First Known Zero-Day 2FA Bypass for Mass Exploitation
ThreatsDay Bulletin: PAN-OS RCE, Mythos cURL Bug, AI Tokenizer Attacks, and 10+ Stories
Windows Zero-Days Expose BitLocker Bypasses And CTFMON Privilege Escalation
⚡ Weekly Recap: Linux Rootkit, macOS Crypto Stealer, WebSocket Skimmers and More
Microsoft Patches 138 Vulnerabilities, Including DNS and Netlogon RCE Flaws
New Fragnesia Linux Kernel LPE Grants Root Access via Page Cache Corruption
Four OpenClaw Flaws Enable Data Theft, Privilege Escalation, and Persistence
[Webinar] How Modern Attack Paths Cross Code, Pipelines, and Cloud
18-Year-Old NGINX Rewrite Module Flaw Enables Unauthenticated RCE
cPanel CVE-2026-41940 Under Active Exploitation to Deploy Filemanager Backdoor
Cisco Catalyst SD-WAN Controller Auth Bypass Actively Exploited to Gain Admin Access
Ollama Out-of-Bounds Read Vulnerability Allows Remote Process Memory Leak
Microsoft's MDASH AI System Finds 16 Windows Flaws Fixed in Patch Tuesday
New Exim BDAT Vulnerability Exposes GnuTLS Builds to Potential Code Execution
⭐ Featured Resources
[eBook] Get the 3-Number SOC Diagnostic to Reduce Queue Risk
[Guide] Stop Email Fraud Before It Turns Into Ransomware Damage
[Webinar] Learn How to Handle Critical SOC Alerts With AI Support
Identify Internal Attack Surfaces More Efficiently With a Free Assessment