Loading vulnerability…
CrashXTS is a Windows BitLocker information disclosure vulnerability in the boot and hibernation workflow. The issue abuses malleability of AES-XTS ciphertext to induce precise corruption of the SYSTEM registry hive during early boot. By corrupting the hive in a controlled way, an attacker can prevent the hibernation file encryption filter from loading. As a result, when the system writes a hibernation file, it is written in plaintext rather than protected as expected. Because the hibernation file can contain BitLocker volume keys and other sensitive memory contents, the flaw can expose secrets that should remain protected at rest.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.