Loading vulnerability…
CVE-2026-53762 affects VeraCrypt builds compiled with the non-default WOLFCRYPT=1 option. In affected builds, VeraCrypt used HKDF with SHA-256/SHA-512 where VeraCrypt's PBKDF2-based derivation was expected, and it did not honor VeraCrypt's configured PBKDF2 iteration count, including the effective Personal Iterations Multiplier (PIM) behavior. The 1.26.29 fix changes WOLFCRYPT=1 builds to use wolfCrypt PBKDF2 instead of HKDF and to honor VeraCrypt's PBKDF2 iteration count. Based on the available information, the issue is a cryptographic implementation/configuration flaw that weakens password-based key derivation for affected builds rather than a memory corruption bug or direct code execution issue.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A VeraCrypt vulnerability fixed in version 1.26.29 that affects only builds compiled with the WOLFCRYPT=1 option, which is not enabled by default.
A VeraCrypt vulnerability fixed in version 1.26.29 that only affects builds compiled with the non-default WOLFCRYPT=1 option.
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.