Windows BitLocker Security Feature Bypass Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.0.26100.8655, 10.0.26200.8655, 10.0.28000.2269, 10.0.26100.32995
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 12 proofs of concept on GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Microsoft Windows 11 Version 24H2
From 10.0.26100.0 · fixed in 10.0.26100.8655
- Microsoft Windows 11 Version 25H2
From 10.0.26200.0 · fixed in 10.0.26200.8655
- Microsoft Windows 11 version 26H1
From 10.0.28000.0 · fixed in 10.0.28000.2269
- Microsoft Windows Server 2025
From 10.0.26100.0 · fixed in 10.0.26100.32995
- Microsoft Windows Server 2025 (Server Core installation)
From 10.0.26100.0 · fixed in 10.0.26100.32995