CVE-2026-45585 Details
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.
A security feature bypass vulnerability has been identified in Windows, commonly referred to as 'YellowKey'. This vulnerability allows an attacker with physical access to a device to bypass the BitLocker encryption, potentially gaining access to encrypted data. The vulnerability affects multiple versions of Windows 11 and Windows Server 2025, both in standard and Server Core installations.
Users can mitigate this vulnerability by adding a PIN to their BitLocker protection. For devices already encrypted with a TPM-only protector, instructions are available for using PowerShell, the command line, or the Control Panel to add a PIN. For devices not yet encrypted, guidance is provided for using Microsoft Intune or Group Policies to configure BitLocker settings that require a PIN at startup.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 20, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/Nightmare-Eclipse/YellowKey | CISA-ADP | ExploitThird Party Advisory |
| https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585 | [email protected] | MitigationVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-77 | Improper Neutralization of Special Elements used in a Command ('Command Injection') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| microsoft windows 11 24h2 | All versions |
CPE
Remediation
| |
| microsoft windows 11 25h2 | All versions |
CPE
Remediation
| |
| microsoft windows 11 26h1 | All versions |
CPE
Remediation
| |
| microsoft windows server 2025 | All versions |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 24, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 22, 2026 | CVE Modified | [email protected] |
| May 20, 2026 | Initial Analysis | [email protected] |
| May 20, 2026 | CVE Modified | CISA-ADP |
| May 20, 2026 | New CVE Received | [email protected] |