Microsoft has confirmed a vulnerability in Windows Recovery Environment that can let an attacker with physical access bypass BitLocker encryption and read the contents of a protected drive. The flaw, tracked as CVE-2026-45585 and nicknamed “YellowKey” by security researchers, carries a CVSS v3.1 base score of 6.8. Microsoft has pushed out interim mitigations but has not yet shipped a full patch, leaving millions of encrypted Windows machines in a precarious spot during the weeks or months it may take for a complete fix to arrive.
That gap matters. BitLocker is the encryption layer protecting laptops and desktops across corporate fleets, government agencies, hospitals, and law firms. If someone steals a BitLocker-protected laptop today, the drive contents are supposed to be unreadable without the correct credentials. YellowKey threatens to change that equation for any device an attacker can physically touch.
What YellowKey actually does
Every Windows installation ships with a built-in recovery environment, known as WinRE, that helps users troubleshoot and repair their systems when the operating system fails to boot. YellowKey exploits a weakness in how that recovery pathway handles BitLocker’s protections. Instead of cracking the encryption key, an attacker sidesteps the lock entirely, using the system’s own recovery tooling as a doorway to the data.
The attack model fits a pattern that researchers have studied for more than 15 years. Princeton University’s Center for Information Technology Policy published landmark research on memory-based attacks against full-disk encryption, demonstrating that encryption keys can persist in RAM long enough to be captured during reboots or mode transitions. YellowKey targets a similar weak moment: the handoff between the normal operating system and the recovery environment, when BitLocker’s defenses are at their thinnest.
The critical distinction is that this is a physical-access attack, not a remote exploit. An attacker needs hands on the device. That limits the scale compared to a worm or a drive-by browser exploit, but it is exactly the scenario that matters most for high-value targets: an executive’s laptop left in a hotel room, a government field device confiscated at a border crossing, or a stolen machine fenced to a buyer who knows what to look for.
What Microsoft has confirmed
Microsoft, acting as the CVE Numbering Authority, assigned CVE-2026-45585 and published a description in the National Vulnerability Database. That listing confirms the flaw resides in Windows Recovery Environment and states that Microsoft is providing mitigations while a full security patch remains in development. No public timeline for the complete fix has been disclosed as of June 2026.
The CVSS 6.8 score places YellowKey in the medium-severity band, which can be misleading. Medium ratings sometimes cause organizations to push a vulnerability down the priority list behind critical-rated flaws scored above 9.0. But the nature of this particular bug complicates that math. A single compromised laptop holding regulated health records, financial data, or classified material could trigger breach-notification obligations, regulatory investigations, or intelligence exposure far out of proportion to a 6.8 number on a spreadsheet.
What we still don’t know
Microsoft has not published a detailed security advisory or technical blog post explaining the root cause beyond the brief CVE description. Without that breakdown, security teams cannot fully evaluate which hardware configurations, firmware versions, or BitLocker deployment modes are most exposed. It is unclear whether certain Trusted Platform Module (TPM) settings or Secure Boot configurations offer better protection than others.
No proof-of-concept exploit code has appeared publicly. The Princeton CITP memory research provides a theoretical foundation for how recovery-mode memory exposures work, but the researchers have not released any statement connecting their earlier work to this specific CVE. Who discovered YellowKey, whether it was an external researcher, Microsoft’s internal security team, or a government partner, has not been disclosed.
It is also unknown whether YellowKey has been exploited in real-world attacks. Microsoft’s CVE entry does not mention active exploitation, and NIST has not published incident data or a dedicated risk bulletin tied to this flaw. The absence of confirmed attacks is not proof that none have occurred; it simply means the public evidence trail stops at the disclosure itself.
Why the ‘medium’ rating undersells the risk
CVSS scores measure technical exploitability, not business impact. A 6.8 reflects the fact that an attacker needs physical proximity rather than a network connection. But for organizations that handle sensitive data on mobile devices, physical-access attacks are not theoretical. They are a routine concern baked into threat models for executives, journalists, defense contractors, and anyone who travels with confidential information on a laptop.
BitLocker adoption is widespread. On Windows Pro and Enterprise editions, device encryption is enabled by default on hardware that meets Microsoft’s requirements. That means a large share of the corporate and government laptop population is potentially in scope. Even consumer devices running Windows 11 with device encryption turned on could be affected, though Microsoft has not clarified the full list of impacted configurations.
Previous BitLocker bypasses offer a useful reference point. In early 2024, Microsoft patched CVE-2024-20666, a separate WinRE-related flaw that also allowed BitLocker circumvention. That fix required updating the recovery environment on every affected machine, a process that proved slow and uneven across large organizations. YellowKey may demand a similarly complex remediation effort once the full patch arrives.
What to do right now
IT administrators should start by applying Microsoft’s published mitigations for CVE-2026-45585 across all BitLocker-protected endpoints. While Microsoft has not detailed every step publicly, the mitigations are expected to restrict how and when the Windows Recovery Environment can be invoked and to harden authentication for recovery operations that could expose disk contents.
Beyond the vendor guidance, several hardening measures can shrink the attack surface immediately:
- Enable pre-boot authentication. Requiring a PIN or password before BitLocker unlocks the drive prevents automatic unlocking based solely on TPM hardware measurements. This is the single most effective step against physical-access attacks on BitLocker.
- Audit WinRE status. Determine which machines have Windows Recovery Environment enabled by default and whether those machines store data sensitive enough to warrant disabling or restricting WinRE until a patch ships.
- Lock down firmware settings. Set strong UEFI/BIOS administrator passwords, disable network boot options, and enforce Secure Boot. These steps limit an attacker’s ability to manipulate the boot sequence.
- Restrict physical USB access. Blocking unauthorized USB devices reduces the risk of booting from external media to attack the recovery environment.
- Treat stolen devices as breaches. Any lost or stolen laptop that may be exposed to a YellowKey-style attack should trigger incident response, including credential revocation and key rotation for accounts and services accessible from that device.
The window that matters most
The period between “mitigations available” and “full patch shipped” is when sophisticated attackers, whether criminal groups or state-sponsored operators, are most likely to move. Physical-access attacks do not scale the way remote exploits do, but they are standard practice in targeted operations against high-value devices. A nation-state intelligence service or a well-resourced corporate espionage team does not need to compromise thousands of machines. One laptop belonging to the right person is enough.
Security teams should brief executives and business-unit leaders in plain terms: YellowKey is not a remote worm that will sweep through the network overnight, but it is a credible way for someone with physical access to a device to read everything on an encrypted drive. That understanding should drive immediate decisions about travel policies, custody of high-value laptops, and the urgency of rolling out mitigations across the fleet.
Until Microsoft delivers a complete fix, disciplined configuration, physical safeguards, and clear communication are the best tools available. The lock on BitLocker has not been broken, but someone has found a way to slip past it through a side door. Closing that door before it gets propped open wider is the job right now.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
