Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-45585Published 2026-05-19

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

mediumPublic exploit10 PoC repos

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)”.

CVSS v3.1
6.8/10Medium
EPSS
0.4%Higher than 40.3% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
4Campaigns referencing it
Priority
7/10Threadlinqs triage score
Published
Updated 2026-11-18
CVSS v3.1 6.8 (MEDIUM) · EPSS 0.4% (higher than 40.3% of all scored CVEs) · Priority 7/10 · Published 2026-05-19

Last updated:

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

Affected products and versions

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

Sources

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

Vendor advisory and patch