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.
Project Subscriptions
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 22 May 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | 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. |
Wed, 20 May 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Microsoft windows 11 25h2
|
|
| CPEs | cpe:2.3:o:microsoft:windows_11_25H2:*:*:*:*:*:*:x64:* | |
| Vendors & Products |
Microsoft windows 11 2h2
|
Microsoft windows 11 25h2
|
Wed, 20 May 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_11_26h1:*:*:*:*:*:*:x64:* |
Wed, 20 May 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
ssvc
|
Wed, 20 May 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Microsoft windows 11 24h2
Microsoft windows 11 25h2 Microsoft windows 11 26h1 Microsoft windows Server 2025 (server Core Installation) |
|
| Vendors & Products |
Microsoft windows 11 24h2
Microsoft windows 11 25h2 Microsoft windows 11 26h1 Microsoft windows Server 2025 (server Core Installation) |
Wed, 20 May 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Windows BitLocker Security Feature Bypass Vulnerability | |
| First Time appeared |
Microsoft
Microsoft windows 11 24h2 Microsoft windows 11 26h1 Microsoft windows 11 2h2 Microsoft windows Server 2025 |
|
| Weaknesses | CWE-77 | |
| CPEs | cpe:2.3:o:microsoft:windows_11_24H2:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_11_26H1:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_11_2H2:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:*:* |
|
| Vendors & Products |
Microsoft
Microsoft windows 11 24h2 Microsoft windows 11 26h1 Microsoft windows 11 2h2 Microsoft windows Server 2025 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: microsoft
Published:
Updated: 2026-05-22T22:04:00.598Z
Reserved: 2026-05-12T19:55:45.729Z
Link: CVE-2026-45585
Updated: 2026-05-20T12:46:25.016Z
Status : Analyzed
Published: 2026-05-20T00:16:44.380
Modified: 2026-05-20T16:42:42.177
Link: CVE-2026-45585
No data.
OpenCVE Enrichment
Updated: 2026-05-23T00:30:05Z