Drooid Logo
Back to story perspectives

Full Breakdown

YellowKey Zero-Day Bypasses BitLocker Encryption on Windows 11 and Server

5/15/2026, 2:36:34 AM

YellowKey Zero-Day Bypasses BitLocker

A custom FsTx folder placed on a USB stick, combined with holding the Ctrl key while booting into the Windows Recovery Environment (WinRE), bypasses the BitLocker recovery key on default Windows 11 and Windows Server 2022/2025 deployments. The exploit opens a command prompt with the encrypted volume already decrypted by the TPM.

Background & Context

BitLocker stores its key in a TPM. WinRE can launch a command shell if its config file is missing. YellowKey uses Transactional NTFS (TxF) to delete that file via a malicious log on a USB drive.

Key Figures & Groups

YellowKey was released by researcher Nightmare-Eclipse (aka Chaotic Eclipse). Independent verification was provided by Kevin Beaumont, Will Dormann of Tharros Labs, and KevTheHermit on X. Microsoft’s internal teams MORSE, MSTIC, GHOST and the Microsoft Security Response Centre (MSRC) are mentioned in the disclosures.

Data & Statistics

Affected platforms: Windows 11, Windows Server 2022, Windows Server 2025. Unaffected: Windows 10. Exploit steps: copy the FsTx folder to a USB, insert it, reboot, hold Ctrl. Reproduced on Windows 11 build 10.0.26100.1. BitLocker is mandatory for many organizations, including government contractors.

Official Statements & Responses

Microsoft stated, “We have a customer commitment to investigate reported security issues and update impacted devices to protect customers as soon as possible. We also support coordinated vulnerability disclosure.” No CVE has been assigned and Microsoft has not publicly acknowledged YellowKey.

Criticism & Opposition

Nightmare-Eclipse claims the bug is an intentional backdoor, writing “huge thanks to MORSE, MSTIC and Microsoft GHOST for making this public disclosure possible.” The researcher also asserts “TPM+PIN does not help” and calls Microsoft’s response “childish.”

On-the-Ground Reports

Will Dormann observed that the FsTx log can delete winpeshl.ini on another volume, forcing WinRE to launch a command prompt with the BitLocker volume unlocked. KevTheHermit posted a successful PoC on X, confirming full access in seconds.

Conflicting Reports & Gaps

The researcher says TPM+PIN does not mitigate, while Dormann suggested it might. The TxF root cause remains unknown, and Microsoft has not issued a patch. Why Windows 10 is unaffected is also unexplained.

Why It Matters

By defeating full-disk encryption, YellowKey exposes data on any device with physical access. Enterprises and agencies relying on BitLocker must reassess threat models and add physical safeguards until a fix is available.

What’s Next

The researcher warned of a “big surprise” for Microsoft on the June 2026 Patch Tuesday. Analysts expect Microsoft may issue an out-of-band WinRE update, but no timeline has been confirmed.

Verbatim Quotes

  • “one of the most insane discoveries I ever found,” — Chaotic Eclipse
  • “Second thing is, no, TPM+PIN does not help, the issue is still exploitable regardless.” — Chaotic Eclipse
  • “I think it will take a while even for MSRC to find the real root cause of the issue.” — Chaotic Eclipse
  • “huge thanks to MORSE, MSTIC and Microsoft GHOST for making this public disclosure possible,” — Nightmare-Eclipse