Loading vulnerability…
CVE-2025-31649 is a hard-coded password vulnerability in the ControlVault WBDI (Windows Biometric Device Interface) Driver used by Dell ControlVault3 prior to version 5.15.14.19 and Dell ControlVault3 Plus prior to version 6.2.36.47. The flaw affects the driver component that mediates access between Windows and the ControlVault hardware security subsystem responsible for biometric devices, smart card functionality, and cryptographic storage. According to the provided content, the vulnerable driver improperly validates authentication for privileged ControlVault API operations due to a hard-coded password or equivalent authentication bypass condition. A specially crafted ControlVault API call can be accepted by the driver and used to execute privileged operations that should require stronger authorization.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced as CVE-2025-31649. Details not specified in the content.
A hard-coded password/authentication bypass vulnerability in the Dell ControlVault3 WBDI driver that allows local attackers to perform privileged operations against the ControlVault hardware security subsystem, potentially extracting cryptographic keys or biometric templates and modifying firmware or biometric 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.