CVE-2026-45585HighMicrosoft CVSS 6.8CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:W/RC:C

Microsoft security update for CVE-2026-45585 — Windows

Published
May 22, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585. This page also shows what EchelonGraph holds for CVE-2026-45585, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products5

  • Windows 11 Version 24H2 for x64-based Systems
  • Windows 11 Version 25H2 for x64-based Systems
  • Windows 11 version 26H1 for x64-based Systems
  • Windows Server 2025
  • Windows Server 2025 (Server Core installation)

✅ Updates Microsoft lists: 3 KB articles

4 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
KB5094125Security Update10.0.26100.32995
KB5094126Security Update10.0.26200.8655
KB5094126Security Update10.0.26100.8655
KB5095051Security Update10.0.28000.2269

🧭 EchelonGraph on CVE-2026-45585

EchelonGraph score
6.8 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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.

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2026-45585, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (7)