CVE-2026-45585
Medium CVSS 6.8Published 2026-05-20 · last changed 2026-07-24
The fix
Microsoft fixes this in updatesKB5087539, KB5094126, KB5089549, KB5095051, KB5094125. The fixed build differs per Windows version, so the row that matters is the one matching the machine you are looking at.
| Windows version | Fixed in build | Update | Released |
|---|---|---|---|
| Windows 11 Version 24H2 for ARM64-based Systems | 10.0.26100.32860 | KB5087539 | 2026-06-09 |
| Windows 11 Version 24H2 for x64-based Systems | 10.0.26100.8655 | KB5094126 | 2026-09-18 |
| Windows 11 Version 25H2 for ARM64-based Systems | 10.0.26200.8457 | KB5089549 | 2026-06-09 |
| Windows 11 Version 25H2 for x64-based Systems | 10.0.26200.8655 | KB5094126 | 2026-09-18 |
| Windows 11 Version 26H1 for ARM64-based Systems | 10.0.28000.2269 | KB5095051 | 2026-06-09 |
| Windows 11 version 26H1 for x64-based Systems | 10.0.28000.2269 | KB5095051 | 2026-09-18 |
| Windows Server 2025 | 10.0.26100.32995 | KB5094125 | 2026-09-18 |
| Windows Server 2025 (Server Core installation) | 10.0.26100.32995 | KB5094125 | 2026-09-18 |
Having the KB is not the same as knowing whether a machine has it. Windows updates supersede each other, so the update you installed often covers a fix that shipped in an earlier one. Paste your build into the patch checker and it walks that chain for you.
What it is
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.
Sources
CVSS vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H