Loading vulnerability…
CVE-2026-45585, publicly referred to as YellowKey, is a Windows BitLocker security feature bypass vulnerability. Microsoft’s advisory states that exploitation requires physical access to the target device and that systems using TPM+PIN are not exploitable. Supporting reporting indicates the issue abuses Windows Recovery Environment (WinRE) behavior to bypass BitLocker Device Encryption and access data on encrypted volumes on affected Windows systems. Microsoft published mitigation guidance before the security update was available after a proof-of-concept was publicly released.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 26 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
102 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Microsoft Defender vulnerability previously disclosed by the same researcher and addressed during June Patch Tuesday.
Publicly disclosed 0-day vulnerability referenced as YellowKey.
A Windows BitLocker bypass previously released by Chaotic Eclipse; Microsoft released patches for it in Patch Tuesday updates.
A recently patched BitLocker bypass vulnerability, referred to as YellowKey, that weaponized WinRE to access encrypted volumes via physical access.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.