CVE-2026-45585 json
Windows BitLocker Security Feature Bypass Vulnerability
published 2026-05-19 5 mo ago modified 2026-08-10 2 mo ago also EUVD-2026-31006
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Microsoft Windows 11 Version 24H2 10.0.26100.8655
- Microsoft Windows 11 Version 25H2 10.0.26200.8655
- Microsoft Windows 11 version 26H1 10.0.28000.2269
- Microsoft Windows Server 2025 10.0.26100.32995
- Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.32995
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 5 mo ago
Exploit prediction
1.89% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/Nightmare-Eclipse/YellowKey referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:W/RC:C |
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Windows 11 Version 24H2
- Microsoft Windows 11 Version 25H2
- Microsoft Windows 11 version 26H1
- Microsoft Windows Server 2025
- Microsoft Windows Server 2025 (Server Core installation)
Classification
- Weakness
-
- CWE-77 Improper Neutralization of Special Elements used in a Command
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-45585
vendor-advisory, patch, mitigation
-
github.com
/Nightmare-Eclipse/YellowKey
exploit, third-party-advisory
Sources
- CVE List CVE-2026-45585
- NVD CVE-2026-45585
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.