Koffei

CVE-2026-45585

🟠 Medium

Windows 11 Version 24H2 ; Windows 11 Version 25H2 ; Windows 11 version 26H1 +2 more · Windows 11 24H2/25H2/26H1 / Server 2025 — builds prior to the patch (e.g. 10.0.26100 < 10.0.26100.8655 ; 10.0.26200 < 10.0.26200.8655)

CVSS (Koffei note)
6.8
CVSS (v3.1, CVE List)
6.8
EPSS (2026-11-18)
1.891%
80.00th percentile

Exploitation

Probable — public PoC (SSVC: poc)

Timeline

  1. 19/05/2026CVE record published (CVE List)

Risk

6.8 Medium (v3.1) — AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:W/RC:C, EPSS 0.491% (CWE-77 : Windows BitLocker security feature bypass publicly known as "YellowKey"; PoC public. Mitigation guidance issued until the security update is available. TPM+PIN )

Fix

Yes — Update Windows (26100.8655 / 26200.8655) ; temporary mitigation ; TPM+PIN protects (advisory)

Official description

Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as &quot;YellowKey&quot;. 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.

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

CWE-77