VeraCrypt up to 1.26.29 Metadata IOCTL Handlers src/Driver/Ntdriver.c information disclosure

Summaryinfo

A vulnerability was found in VeraCrypt up to 1.26.29. It has been classified as problematic. This affects an unknown function of the file src/Driver/Ntdriver.c of the component Metadata IOCTL Handlers. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2026-77572. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability classified as problematic was found in VeraCrypt up to 1.26.29. Affected by this vulnerability is an unknown code block of the file src/Driver/Ntdriver.c of the component Metadata IOCTL Handlers. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

VeraCrypt provides disk encryption with strong security based on TrueCrypt. In 1.26.29 and earlier, selected metadata IOCTL handlers in the VeraCrypt Windows veracrypt.sys driver accept caller-supplied object-manager and device paths broader than supported VeraCrypt workflows require. A local user who can open the intentionally user-accessible \.\VeraCrypt device can use TC_IOCTL_GET_RESOLVED_SYMLINK, TC_IOCTL_GET_DRIVE_PARTITION_INFO, VC_IOCTL_GET_DRIVE_GEOMETRY_EX, or the legacy TC_IOCTL_GET_DRIVE_GEOMETRY handler to make src/Driver/Ntdriver.c perform kernel-context symbolic-link or disk-device lookups outside the intended path scope. This can disclose low-sensitivity drive-letter targets, partition information, disk geometry, GPT or MBR state, and limited object-manager path metadata.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-77572 since 08/20/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• VeraCrypt

Version

• 1.26.0
• 1.26.1
• 1.26.2
• 1.26.3
• 1.26.4
• 1.26.5
• 1.26.6
• 1.26.7
• 1.26.8
• 1.26.9
• 1.26.10
• 1.26.11
• 1.26.12
• 1.26.13
• 1.26.14
• 1.26.15
• 1.26.16
• 1.26.17
• 1.26.18
• 1.26.19
• 1.26.20
• 1.26.21
• 1.26.22
• 1.26.23
• 1.26.24
• 1.26.25
• 1.26.26
• 1.26.27
• 1.26.28
• 1.26.29

Website

• Product: https://github.com/veracrypt/VeraCrypt/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion