CVE-2026-45585 Windows BitLocker Security Feature Bypass Vulnerability
Attackers can bypass BitLocker encryption to access data on stolen or compromised Windows devices, requiring immediate mitigation or patching.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-45585?
CVE-2026-45585 is a medium-severity vulnerability in Microsoft Windows 11 24h2, published on 19 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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. Mitigation FAQs Should I leverage the temporary mitigation? Microsoft recommends that you consider implementing these mitigations if you are concerned your devices and data are at risk of being compromised or stolen. For example, if your organization’s employees take their work devices home or on business travel. What impact to service availability/management could be caused by implementing the mitigations? Implementing these mitigations will not impact service availability or management operations. Do customers need to revert the changes made to mitigate the vulnerability once the security update to protect against this vulnerability is available? No. The security update will maintain the mitigation's behavior once the security update is installed. I am using TPM+PIN, am I at risk of this vulnerability being exploited No, if you are using TPM+PIN the vulnerability is not exploitable.
Weakness: CWE-77
Which versions are affected by CVE-2026-45585?
It affects 4 products.
Products include Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows 11 26h1, Microsoft Windows Server 2025.
How do I fix CVE-2026-45585?
No fix has been published for CVE-2026-45585 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-45585 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45585 exists.
Public exploit code: 12 proofs of concept on GitHub.
Other vulnerabilities in Microsoft Windows 11 24h2
- CVE-2025-60710 Microsoft Windows Link Following
- CVE-2026-54990 Remote Desktop Client Remote Code Execution Vulnerability
- CVE-2025-50165 Windows Graphics Component Remote Code Execution Vulnerability
- CVE-2025-21311 Windows NTLM V1 Elevation of Privilege Vulnerability
- CVE-2026-108463 Windows SmartScreen Security Feature Bypass Vulnerability
Sources
Also known as GHSA-2h24-8rjh-qgjv.