YellowKey BitLocker Bypass Requires Physical Access, Significantly Reduces Enterprise Disk Encryption Assurance
YellowKey, a publicly disclosed exploit, reliably bypasses Windows 11 BitLocker default configurations by exploiting TPM-based key storage, but requires physical device access. This substantially weakens encryption guarantees for organisations relying on BitLocker as a mandatory protection.
Affected
YellowKey represents a functional break in BitLocker's security model when deployed with default Windows 11 configuration. The exploit, published by researcher Nightmare-Eclipse on GitHub, reliably circumvents the encryption by targeting the Trusted Platform Module (TPM) where BitLocker stores its volume encryption key. Although the attack requires physical device access, this is a critical assumption that many organisations have incorrectly treated as sufficient defence; attackers with brief offline access to a laptop or server can now extract encrypted disk contents.
The technical specifics suggest the vulnerability exploits the TPM's integration with BitLocker rather than breaking the underlying AES encryption. Default Windows 11 deployments may fail to enforce additional security measures such as PIN-based protections or suspension of BitLocker during key rotation cycles. TPM implementations themselves vary by manufacturer and firmware, meaning some devices may be more vulnerable than others, but the publicly released exploit appears to work across common enterprise deployments.
Organisations with mandatory BitLocker policies face immediate risk. Government contractors, regulated industries, and enterprises handling sensitive data have standardised on BitLocker as part of compliance frameworks. The assumption that physical security controls are sufficient to prevent disk access is now invalidated. This is particularly acute for distributed workforces where devices travel, for forensic scenarios where storage is seized, and for managed device fleets where disposal procedures assume encryption remains intact.
Defenders should prioritise: enabling BitLocker startup PIN requirements even on TPM-only deployments; ensuring TPM firmware is current; auditing whether BitLocker is actually enforcing TPM version 2.0 with measured boot; and assessing whether additional encryption layers above BitLocker are warranted for high-value data. Security teams should also review whether physical security controls are adequate given this capability now exists in public domain tooling.
The broader implication is that hardware-backed key storage is only as strong as its integration layer. BitLocker's reliance on TPM for default configurations creates a single point of failure that researchers have now weaponised. This reinforces that encryption schemes must assume motivated adversaries with physical access, and that organisational controls cannot substitute for cryptographic design that resists local compromise.
Sources