Windows BitLocker Security Feature Bypass Vulnerability
Key facts
- Attack vector
- Physical
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Microsoft. Impact type from Microsoft.
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 to before 10.0.26100.8655 | 10.0.26100.8655 | Patch available | CNA |
| Microsoft | Windows 11 Version 25H2 | 10.0.26200.0 to before 10.0.26200.8655 | 10.0.26200.8655 | Patch available | CNA |
| Microsoft | Windows 11 version 26H1 | 10.0.28000.0 to before 10.0.28000.2269 | 10.0.28000.2269 | Patch available | CNA |
| Microsoft | Windows Server 2025 | 10.0.26100.0 to before 10.0.26100.32995 | 10.0.26100.32995 | Patch available | CNA |
| Microsoft | Windows Server 2025 (Server Core installation) | 10.0.26100.0 to before 10.0.26100.32995 | 10.0.26100.32995 | Patch available | CNA |
- Windows 11 Version 24H2 VendorMicrosoft Affected 10.0.26100.0 to before 10.0.26100.8655 Fixed in 10.0.26100.8655 Patch available CNA
- Windows 11 Version 25H2 VendorMicrosoft Affected 10.0.26200.0 to before 10.0.26200.8655 Fixed in 10.0.26200.8655 Patch available CNA
- Windows 11 version 26H1 VendorMicrosoft Affected 10.0.28000.0 to before 10.0.28000.2269 Fixed in 10.0.28000.2269 Patch available CNA
- Windows Server 2025 VendorMicrosoft Affected 10.0.26100.0 to before 10.0.26100.32995 Fixed in 10.0.26100.32995 Patch available CNA
- Windows Server 2025 (Server Core installation) VendorMicrosoft Affected 10.0.26100.0 to before 10.0.26100.32995 Fixed in 10.0.26100.32995 Patch available CNA
CPE configurations NVD · 4
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:x64:* | all versions | Vulnerable | Microsoft |
| cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:x64:* | all versions | Vulnerable | Microsoft |
| cpe:2.3:o:microsoft:windows_11_26h1:*:*:*:*:*:*:x64:* | all versions | Vulnerable | Microsoft |
| cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:*:* | all versions | Vulnerable | Microsoft |
- cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:x64:* Versions all versions Vulnerable ·Microsoft
- cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:x64:* Versions all versions Vulnerable ·Microsoft
- cpe:2.3:o:microsoft:windows_11_26h1:*:*:*:*:*:*:x64:* Versions all versions Vulnerable ·Microsoft
- cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:*:* Versions all versions Vulnerable ·Microsoft
Remediation
Microsoft 3 updates
- Security Update
- Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2269
- Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269
- Security Update
- Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.8655
- Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8655
- Windows 11 Version 25H2 for ARM64-based Systems 10.0.26200.8655
- Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8655
- Windows Server 2025 10.0.26100.8655
- Windows Server 2025 (Server Core installation) 10.0.26100.8655
- Security Update
- Windows Server 2025 10.0.26100.32995
- Windows Server 2025 (Server Core installation) 10.0.26100.32995
Vendor assessments
Microsoft
Microsoft's page for this CVE →
- Impact
- Security Feature Bypass
- Exploited
- No
- Publicly disclosed
- Yes
- Exploitability
- Exploitation More Likely
Timeline
- 2026-10-02 Threatist record created from CVE-2026-45585
- 2026-10-03 Alias added: GHSA-2h24-8rjh-qgjv
- 2026-10-25 EPSS moved to the 50th–90th percentile
References
More Microsoft Windows 11 24h2 vulnerabilities
- TI-2026-26194 Windows Internet Key Exchange (IKE) Service Extensions Remote Code Execution Vulnerability KEVCVSS 3.1CRITICAL 9.8
- TI-2026-73128 Windows Shell Security Feature Bypass Vulnerability KEVCVSS 3.1HIGH 8.8
- TI-2026-17367 MSHTML Framework Security Feature Bypass Vulnerability KEVCVSS 3.1HIGH 8.8
- TI-2026-17364 Windows Shell Security Feature Bypass Vulnerability KEVCVSS 3.1HIGH 8.8
- TI-2025-24062 Windows SMB Client Elevation of Privilege Vulnerability KEVCVSS 3.1HIGH 8.8
- TI-2025-24042 Internet Shortcut Files Remote Code Execution Vulnerability KEVCVSS 3.1HIGH 8.8
Sources
- CVE-2026-45585 · CVE Program
- CVE-2026-45585 · NVD
- FIRST EPSS
- GHSA-2h24-8rjh-qgjv · GitHub Advisory Database · CC BY 4.0
- CVE-2026-45585 · Microsoft Security Update Guide
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences