Veracrypt
Monthly
VeraCrypt 1.26.29 (FUSE-T build) on macOS can leave a dismounted volume's decrypted contents readable, because VeraCrypt fails to terminate the FUSE-T auxiliary service (go-nfsv4) and its associated core-service helper processes, which keep serving the decrypted volume image (volume.dmg) over a loopback SMB session while retaining an open handle to the underlying raw device. An authenticated local user or process on the same host can then re-attach volume.dmg from the stale auxiliary mount, or simply reopen a previously accessed path (for example from the macOS Open Recent menu), and read the decrypted volume without supplying the passphrase again. The issue is specific to the FUSE-T build - the macFUSE build is explicitly unaffected - and requires that a volume was previously mounted and dismounted on that machine; no public exploit code and no confirmed active exploitation have been identified at time of analysis.
Information disclosure in the VeraCrypt Windows kernel driver (veracrypt.sys) in version 1.26.29 and earlier allows a locally authenticated, low-privileged user to supply crafted object-manager or device paths to the TC_IOCTL_GET_RESOLVED_SYMLINK, TC_IOCTL_GET_DRIVE_PARTITION_INFO, VC_IOCTL_GET_DRIVE_GEOMETRY_EX, and legacy TC_IOCTL_GET_DRIVE_GEOMETRY handlers, causing src/Driver/Ntdriver.c to perform kernel-context symbolic-link and disk-device lookups outside the intended VeraCrypt workflow scope. Successful abuse discloses only low-sensitivity metadata - drive-letter targets, partition information, disk geometry, GPT/MBR state, and limited object-manager path metadata - with no integrity or availability impact, which is why the issue carries a low CVSS 3.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). Exploitation is strictly local, requiring an interactive session or code execution as any user account on a host running an affected driver; no public exploit code identified at time of analysis, and the issue is fully neutralized on hosts updated past the upstream fixing commit.
Hidden volume creation in VeraCrypt 1.26.6 through 1.26.28 leaves forensically detectable plaintext markers inside file-hosted hidden volume containers, directly undermining plausible deniability guarantees. The FormatNoFs and FormatFat functions apply a quick-format optimization that writes zeroed sectors at predictable 128 MiB intervals via WriteFile, bypassing the EncryptDataUnits path that would fill the area with indistinguishable ciphertext; a forensic examiner with access to the container can identify these anomalous plaintext artifacts and infer hidden volume presence. Encryption strength and hidden-volume contents are not compromised - impact is confined to deniability failure. No public exploit has been identified and this vulnerability is not listed in CISA KEV.
Key derivation in VeraCrypt's non-default wolfCrypt backend silently substituted HKDF for PBKDF2-HMAC in SHA-256 and SHA-512 volume-header derivation, discarding the configured iteration count entirely - meaning any PIM or iteration tuning applied by users of affected builds provided zero additional brute-force resistance. Any attacker who obtains a volume file produced by a WOLFCRYPT=1 source build can attempt password recovery at HKDF speeds rather than PBKDF2-iterated cost, dramatically reducing the work factor. Official precompiled VeraCrypt binaries and standard distribution packages are entirely unaffected; no public exploit has been identified and this vulnerability is not listed in CISA KEV.
VeraCrypt 1.24 allows Local Privilege Escalation during execution of VeraCryptExpander.exe. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity.
IDRIX, Truecrypt Veracrypt, Truecrypt Prior to 1.23-Hotfix-1 (Veracrypt), all versions (Truecrypt) is affected by: Buffer Overflow. Rated low severity (CVSS 3.3), this vulnerability is low attack complexity.
The (1) IsVolumeAccessibleByCurrentUser and (2) MountDevice methods in Ntdriver.c in TrueCrypt 7.0, VeraCrypt before 1.15, and CipherShed, when running on Windows, do not check the impersonation. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
The IsDriveLetterAvailable method in Driver/Ntdriver.c in TrueCrypt 7.0, VeraCrypt before 1.15, and CipherShed, when running on Windows, does not properly validate drive letter symbolic links, which. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
Untrusted search path vulnerability in the installer for TrueCrypt 7.2 and 7.1a, VeraCrypt before 1.17-BETA, and possibly other products allows local users to execute arbitrary code with. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. Public exploit code available.
VeraCrypt 1.26.29 (FUSE-T build) on macOS can leave a dismounted volume's decrypted contents readable, because VeraCrypt fails to terminate the FUSE-T auxiliary service (go-nfsv4) and its associated core-service helper processes, which keep serving the decrypted volume image (volume.dmg) over a loopback SMB session while retaining an open handle to the underlying raw device. An authenticated local user or process on the same host can then re-attach volume.dmg from the stale auxiliary mount, or simply reopen a previously accessed path (for example from the macOS Open Recent menu), and read the decrypted volume without supplying the passphrase again. The issue is specific to the FUSE-T build - the macFUSE build is explicitly unaffected - and requires that a volume was previously mounted and dismounted on that machine; no public exploit code and no confirmed active exploitation have been identified at time of analysis.
Information disclosure in the VeraCrypt Windows kernel driver (veracrypt.sys) in version 1.26.29 and earlier allows a locally authenticated, low-privileged user to supply crafted object-manager or device paths to the TC_IOCTL_GET_RESOLVED_SYMLINK, TC_IOCTL_GET_DRIVE_PARTITION_INFO, VC_IOCTL_GET_DRIVE_GEOMETRY_EX, and legacy TC_IOCTL_GET_DRIVE_GEOMETRY handlers, causing src/Driver/Ntdriver.c to perform kernel-context symbolic-link and disk-device lookups outside the intended VeraCrypt workflow scope. Successful abuse discloses only low-sensitivity metadata - drive-letter targets, partition information, disk geometry, GPT/MBR state, and limited object-manager path metadata - with no integrity or availability impact, which is why the issue carries a low CVSS 3.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). Exploitation is strictly local, requiring an interactive session or code execution as any user account on a host running an affected driver; no public exploit code identified at time of analysis, and the issue is fully neutralized on hosts updated past the upstream fixing commit.
Hidden volume creation in VeraCrypt 1.26.6 through 1.26.28 leaves forensically detectable plaintext markers inside file-hosted hidden volume containers, directly undermining plausible deniability guarantees. The FormatNoFs and FormatFat functions apply a quick-format optimization that writes zeroed sectors at predictable 128 MiB intervals via WriteFile, bypassing the EncryptDataUnits path that would fill the area with indistinguishable ciphertext; a forensic examiner with access to the container can identify these anomalous plaintext artifacts and infer hidden volume presence. Encryption strength and hidden-volume contents are not compromised - impact is confined to deniability failure. No public exploit has been identified and this vulnerability is not listed in CISA KEV.
Key derivation in VeraCrypt's non-default wolfCrypt backend silently substituted HKDF for PBKDF2-HMAC in SHA-256 and SHA-512 volume-header derivation, discarding the configured iteration count entirely - meaning any PIM or iteration tuning applied by users of affected builds provided zero additional brute-force resistance. Any attacker who obtains a volume file produced by a WOLFCRYPT=1 source build can attempt password recovery at HKDF speeds rather than PBKDF2-iterated cost, dramatically reducing the work factor. Official precompiled VeraCrypt binaries and standard distribution packages are entirely unaffected; no public exploit has been identified and this vulnerability is not listed in CISA KEV.
VeraCrypt 1.24 allows Local Privilege Escalation during execution of VeraCryptExpander.exe. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity.
IDRIX, Truecrypt Veracrypt, Truecrypt Prior to 1.23-Hotfix-1 (Veracrypt), all versions (Truecrypt) is affected by: Buffer Overflow. Rated low severity (CVSS 3.3), this vulnerability is low attack complexity.
The (1) IsVolumeAccessibleByCurrentUser and (2) MountDevice methods in Ntdriver.c in TrueCrypt 7.0, VeraCrypt before 1.15, and CipherShed, when running on Windows, do not check the impersonation. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
The IsDriveLetterAvailable method in Driver/Ntdriver.c in TrueCrypt 7.0, VeraCrypt before 1.15, and CipherShed, when running on Windows, does not properly validate drive letter symbolic links, which. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
Untrusted search path vulnerability in the installer for TrueCrypt 7.2 and 7.1a, VeraCrypt before 1.17-BETA, and possibly other products allows local users to execute arbitrary code with. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. Public exploit code available.