veracrypt VeraCrypt hidden-volume formatting weakens plausible deniability

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-54073?

CVE-2026-54073 is a vulnerability classified as Protection Mechanism Failure, affecting VeraCrypt (affected versions: >= 1.26.6, < 1.26.29). This vulnerability is rated Medium, with a CVSS score of 4.6. Public exploit code or evidence is available for this vulnerability, but that does not confirm exploitation in the wild.

Overview

Original source data

VeraCrypt provides disk encryption with strong security based on TrueCrypt. From 1.26.6 until 1.26.29, file-hosted hidden volume creation forces quick format and the FormatNoFs function in src/Common/Format.c and FormatFat function in src/Common/Fat.c use WriteFile to place raw zeroed sectors at predictable 128 MiB intervals. These writes bypass the normal EncryptDataUnits formatting path, leaving deterministic plaintext markers in an area expected to resemble random ciphertext. The markers can weaken plausible deniability during forensic inspection, although they do not disclose hidden-volume content or reduce the strength of VeraCrypt encryption. This issue is fixed in version 1.26.29.

Affected products and scope

  • Affected product: veracrypt VeraCrypt versions >= 1.26.6, < 1.26.29 when creating file-hosted hidden volumes.
  • The vendor advisory describes the affected span as 1.26.6 through 1.26.28, consistent with the normalized upper boundary of < 1.26.29.
  • The issue is fixed in 1.26.29.
  • The behavior is described in the Windows file-container formatting path; the record identifies no additional package or parallel branch. The status of unlisted branches should not be inferred from this fix.

Technical details

During creation of a file-hosted hidden volume, VeraCrypt forces quick formatting. In the affected file-container branches, FormatNoFs() and FormatFat() call WriteFile() directly with a zeroed sector buffer at predictable 128 MiB intervals instead of using the formatting path that applies EncryptDataUnits(). The result can be raw zero sectors in the hidden-volume data area where the contents are expected to resemble random ciphertext. The relevant user-controlled conditions are creation of a file-hosted hidden volume and use of the no-filesystem or FAT formatting path; hidden-volume creation forces quick format internally, so a separate quick-format selection is not required. This is a protection mechanism failure that weakens plausible deniability, but it does not disclose hidden-volume content or reduce encryption strength. The fix makes these branches skip the allocation shortcut for hidden volumes while retaining the shortcut for non-hidden file containers and using the encrypted formatter write path.

Exploitability

The issue has local reachability and is not described as a remotely reachable network service flaw. The public advisory includes a PoC that requires a user to create a qualifying file-hosted hidden volume and then inspect the host file at the relevant locations; this requires user interaction but does not require prior special privileges according to the supplied information. The PoC can reveal zeroed sectors at predictable 128 MiB intervals rather than reading or decrypting hidden-volume content. The available evidence establishes a public PoC, but it does not establish real-world exploitation in a named campaign, victim environment, or breach.

Technical impact

The technical outcome is that the host file can contain deterministic plaintext markers in an area expected to contain random-looking ciphertext. A forensic examiner with access to the container may infer that the hidden volume does not fully match plausible-deniability expectations, weakening the property that conceals the existence of protected data. There is no evidence that the flaw provides access to hidden-volume content or weakens VeraCrypt's encryption algorithms. The record does not identify direct impact to integrity, availability, code execution, or privilege escalation.

Business impact

Organizations relying on VeraCrypt hidden volumes may lose part of the plausible-deniability property used to conceal the existence of sensitive data. A forensic examination of a host file could reveal deterministic markers and produce evidence inconsistent with the hidden-volume threat model. This may increase the risk of scrutiny or require reassessment of related containers during an investigation. The issue does not by itself establish that protected data was read, decrypted, or modified.

Remediation

  1. Upgrade VeraCrypt to the fixed release 1.26.29.
  2. Inventory file-hosted hidden volumes created with affected releases, prioritizing volumes that used the no-filesystem or FAT formatting path.
  3. Where plausible deniability is material, perform a controlled forensic review of relevant host files for zero markers at the intervals described by the advisory.
  4. Evaluate findings under the organization's sensitive-data handling policy. A marker indicates a plausible-deniability risk, not a cryptographic compromise.
  5. The supplied record and advisory provide no separate workaround beyond using the fixed release.

Detection

  1. Inventory VeraCrypt installations and compare them with the affected and fixed boundaries listed in affected_summary.
  2. Identify file-hosted hidden volumes created while an affected release was in use, with particular attention to volumes larger than 128 MiB.
  3. Record whether the hidden volume used the no-filesystem or FAT path, because these are the FormatNoFs() and FormatFat() paths described by the advisory.
  4. During a controlled forensic review, inspect the host file at predictable 128 MiB intervals for zeroed sectors in the hidden-volume data area.
  5. Treat deterministic zero markers as evidence of the formatting weakness and a plausible-deniability risk, not as evidence that hidden-volume content was read or decrypted. The available evidence does not establish a product-specific log event or IOC.
Sources (17)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.