CVE-2026-45585

mediumpriority · track · 11EPSS 0.019 · 79 %ileexploit · PoCDEEUNLRUUS
grimoire priorityP1 · Urgent
Exploitable?
Public exploit
12 exploits · PoC
Likely / severe?
1.89% (79th) EPSS
CVSS 6.8 · medium
Is it mine?
34 products
Check your exposure
Who says so?
6 sources
cnnvd · enisa_euvd · fstec_bdu · cert_bund

EPSS · scored 2026-10-27

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.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

02

cvss

Technical severity, 0–10. One row per scoring source.

6.8
010

base score 0–10 · higher = more severe · hover a vector to decode

v3.16.8mediumAV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · FSTEC (BDU) RU
v3.16.8mediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:W/RC:Csecondary · ENISA EU
v3.16.8mediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · secure@microsoft.com USexploitability 0.9 · impact 5.9
v3.16.4mediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:Psecondary · CVSS-BT (t0sche)
v3.16.8mediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:W/RC:Csecondary · NCSC-NL NL
v3.16.8mediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:W/RC:Csecondary · Microsoft Security Response Center US
03

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: poc · Automatable: no · Technical Impact: totalcoordinatorcisa_ssvcUS
04

weaknesses

The CWE weakness classes this flaw belongs to.

05

exploits (12)

Public proof-of-concept and weaponised exploit code.

06

affected products (34)

Products and version ranges known to be affected.

showing 20 of 34
07

advisories (3)

Vendor and ecosystem advisories describing this.

  • NCSC-2026-0165Kwetsbaarheid aangetroffen in Microsoft WindowsNL2026-05-20csaf · ncsc_nlNL

    Microsoft heeft maatregelen gepubliceerd voor een kwetsbaarheid in Windows besturingssystemen waarmee lokale kwaadwillenden toegang kunnen krijgen tot data die via BitLocker is versleuteld.

  • WID-SEC-W-2026-1609Microsoft Windows 11 und Windows Server 2025: Schwachstelle ermöglicht Umgehen der LaufwerksverschlüsselungDeutsch2026-05-19csaf · cert_bundDE

    Ein Angreifer mit physischem Zugriff kann eine Schwachstelle in Microsoft Windows 11 und Microsoft Windows Server 2025 ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

  • msrc_CVE-2026-45585Windows BitLocker Security Feature Bypass Vulnerability2026-05-19csaf · msrc_csafUS

    To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

08

also known as (4)

Other names and identifiers for this entity.

09

sources

Which sources assert this record, and when.

10

references (5)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan