# CVE-2026-45585 — Microsoft Windows 11 Version 24H2

> As of 2026-11-18, CVE-2026-45585 is a MEDIUM-severity vulnerability in Microsoft Windows 11 Version 24H2, CVSS v3.1 6.8, EPSS 0.4% (40.3th percentile). Threadlinqs Intelligence links 4 tracked threat campaigns to CVE-2026-45585, most recently “"Hello Again" Attack Bypasses Windows Hello and BitLocker PIN Lockout via TPM State Rollback (CVE-2026-43613)”.

**Last updated:** 2026-11-18

## What is CVE-2026-45585?

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.

The record classifies CVE-2026-45585 under weakness class [CWE-77](https://intel.threadlinqs.com/cwe/CWE-77). Its CVSS v3 base vector states that the flaw requires physical access to the device, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 5 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 184 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 6.8 — MEDIUM (`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`)
- **EPSS (FIRST):** 0.4% probability of exploitation in the next 30 days, higher than 40.3% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-05-19

## Is CVE-2026-45585 being exploited?

Weaponised exploit code for CVE-2026-45585 is publicly available. 10 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 33 in the Threadlinqs vulnerability feed.

- [Desireeontrial76/yellowkey-bitlocker](https://github.com/Desireeontrial76/yellowkey-bitlocker) (github)
- [andrei-majer/bitlocker-hardening](https://github.com/andrei-majer/bitlocker-hardening) (github)
- [YellowKeyBitLocker-CVE/YellowKey-BitLocker-CVE-2026-45585](https://github.com/YellowKeyBitLocker-CVE/YellowKey-BitLocker-CVE-2026-45585) (github)
- [everest90909/YellowKey-WinRE-Remediation](https://github.com/everest90909/YellowKey-WinRE-Remediation) (github)
- [0xBlackash/CVE-2026-45585](https://github.com/0xBlackash/CVE-2026-45585) (github)
- [bjbakker1984/Yellowkey-mitigation](https://github.com/bjbakker1984/Yellowkey-mitigation) (github)
- [ChanderManiPandey2022/Yellow-Key-Check](https://github.com/ChanderManiPandey2022/Yellow-Key-Check) (github)
- [ChanderManiPandey2022/YellowKey-BitLocker-Bypass-CVE-2026-45585-Detect-Fix-Automatically-via-Microsoft-Intune](https://github.com/ChanderManiPandey2022/YellowKey-BitLocker-Bypass-CVE-2026-45585-Detect-Fix-Automatically-via-Microsoft-Intune) (github)

## Affected products and versions

- [Microsoft](https://intel.threadlinqs.com/vendors/microsoft): Windows 11 Version 24H2, Windows 11 Version 25H2, Windows 11 version 26H1, Windows Server 2025, Windows Server 2025 (Server Core installation)

## How to fix CVE-2026-45585

Patch reference: [https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-45585

4 tracked threats in the Threadlinqs corpus reference CVE-2026-45585, either in the campaign’s CVE list or as an indicator on the campaign record.

- ["Hello Again" Attack Bypasses Windows Hello and BitLocker PIN Lockout via TPM State Rollback (CVE-2026-43613)](https://intel.threadlinqs.com/threat/TL-2026-6384) — MEDIUM · 2026-11-18
- [NightmareEclipse Coordinated Disclosure Breach Campaign: 9+ Windows Zero-Days (CVE-2026-33825, CVE-2026-41091, CVE-2026-45498, CVE-2026-45585, CVE-2026-45586) Dumped Outside Responsible Disclosure and Weaponized in Real-World Intrusions](https://intel.threadlinqs.com/threat/TL-2026-1865) — CRITICAL · 2026-08-04
- [CVE-2026-50661: Windows BitLocker Security Feature Bypass 0-Day](https://intel.threadlinqs.com/threat/TL-2026-1346) — MEDIUM · 2026-07-15
- [Microsoft July 2026 Patch Tuesday: Record 622 CVEs Include Two Actively Exploited Zero-Days in AD FS (CVE-2026-56155) and SharePoint Server (CVE-2026-56164)](https://intel.threadlinqs.com/threat/TL-2026-1331) — CRITICAL · 2026-07-14

## Sources

Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories.

**Vendor advisory and patch**

- [msrc.microsoft.com — vendor advisory](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-45585
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
