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

> Attackers can bypass BitLocker encryption to access data on stolen or compromised Windows devices, requiring immediate mitigation or patching.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-2h24-8rjh-qgjv

## What is CVE-2026-45585?

CVE-2026-45585 is a medium-severity vulnerability in Microsoft Windows 11 24h2, published on 19 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-45585?

It affects 4 products.


Products: Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows 11 26h1, Microsoft Windows Server 2025.

## How do I fix CVE-2026-45585?

No fix has been published for CVE-2026-45585 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45585 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45585 exists.

Public exploit code:

- Manage and recover BitLocker encrypted drives with this tool for Windows 11 recovery key management and educational study of CVE-2026-45585. (github_poc): https://github.com/Desireeontrial76/yellowkey-bitlocker
- BitLocker TPM+PIN Hardening Against CVE-2026-45585 (YellowKey) (github_poc): https://github.com/andrei-majer/bitlocker-hardening
- Intune Remediation package for the CVE-2026-45585 YellowKey BitLocker/WinRE bypass mitigation described in the provided procedure.  This package removes `autofstx.exe` from the offline WinRE image's `BootExecute` value and refreshes WinRE registration so BitLocker trust is reestablished. (github_poc): https://github.com/everest90909/YellowKey-WinRE-Remediation
- CVE-2026-45585 (github_poc): https://github.com/0xredash/CVE-2026-45585
- A small script to apply Yellowkey mitigation based on CVE-2026-45585 instructions (github_poc): https://github.com/bjbakker1984/Yellowkey-mitigation
- YellowKey | BitLocker Bypass Vulnerability (CVE-2026-45585) (github_poc): https://github.com/ChanderManiPandey2022/Yellow-Key-Check

## Other vulnerabilities in Microsoft Windows 11 24h2

- [CVE-2025-60710](https://insights.sbomify.com/CVE-2025-60710/): Microsoft Windows Link Following (high 7.8, exploited in the wild)
- [CVE-2026-54990](https://insights.sbomify.com/CVE-2026-54990/): Remote Desktop Client Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2025-50165](https://insights.sbomify.com/CVE-2025-50165/): Windows Graphics Component Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2025-21311](https://insights.sbomify.com/CVE-2025-21311/): Windows NTLM V1 Elevation of Privilege Vulnerability (critical 9.8)
- [CVE-2026-108463](https://insights.sbomify.com/CVE-2026-108463/): Windows SmartScreen Security Feature Bypass Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45585 and fix it if it is affected.

What it is: CVE-2026-45585 is a medium-severity vulnerability in Microsoft Windows 11 24h2, published on 19 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45585 exists.

Affected product: Microsoft Windows 11 24h2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45585/ (Markdown: https://insights.sbomify.com/CVE-2026-45585/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45585
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45585
- OSV: https://osv.dev/vulnerability/CVE-2026-45585

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45585/
Summaries are generated and may contain mistakes; the official description above is the record.