CVE-2026-77572: VeraCrypt: Missing authorization on veracrypt.sys IOCTLs exposes disk topology, symlink targets, and DeviceObject reference count to any client of \\.\VeraCrypt
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 TCIOCTLGETRESOLVEDSYMLINK, TCIOCTLGETDRIVEPARTITIONINFO, VCIOCTLGETDRIVEGEOMETRYEX, or the legacy TCIOCTLGETDRIVEGEOMETRY 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.
Affected Software
Event History
Frequently Asked Questions
Who can trigger the information disclosure?
A local user who can open the intentionally user-accessible \\.\VeraCrypt device can issue the affected IOCTLs. The issue is in the VeraCrypt Windows driver.
What access and interaction are required for exploitation?
An attacker needs local access and the ability to open the VeraCrypt device, then send one of the affected IOCTL requests with supplied object-manager or device paths. No user interaction is required.
What information could be exposed?
The affected requests can disclose drive-letter targets, partition information, disk geometry, GPT or MBR state, and limited object-manager path metadata. The described impact is limited to low-sensitivity information disclosure.
How can I determine whether a deployment is affected?
Deployments using VeraCrypt 1.26.29 or earlier are affected. The issue applies to the Windows veracrypt.sys driver and its accessible \\.\VeraCrypt device.