Loading vulnerability…
CVE-2026-50661 is a protection-mechanism failure in Windows BitLocker that permits an unauthorized attacker to bypass BitLocker Device Encryption through a physical attack. The flaw affects supported Windows client and server releases prior to the July 2026 security updates and was publicly disclosed before remediation. Microsoft assigned a CVSS v3.1 score of 6.1 (Medium).
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
49 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A BitLocker protection bypass requiring physical access, illustrating compromise through implementation or pre-unlock logic rather than a break of AES-256 itself.
A BitLocker protection bypass vulnerability that could allow someone with physical access to access encrypted data.
A publicly disclosed BitLocker bypass vulnerability that requires physical access to defeat BitLocker protections.
Windows BitLocker security feature bypass zero-day caused by failure of an unspecified protective mechanism, allowing an unauthorized attacker with physical access to bypass encryption and access protected data.
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.