VeraCrypt 1.26.29 (FUSE-T build) on macOS sometimes allows unintended access to decrypted data

Why it is Yellow

• CVSS 7.2 high

References

• https://github.com/veracrypt/VeraCrypt/commit/d7bc65bed004996d299ec76666d1b283a07e2526
• https://github.com/veracrypt/VeraCrypt/issues/1779
• https://github.com/veracrypt/VeraCrypt/issues/1845
• https://github.com/veracrypt/VeraCrypt/pull/1866
• https://github.com/veracrypt/VeraCrypt/releases/tag/VeraCrypt_1.26.29
• https://github.com/veracrypt/VeraCrypt/security/advisories/GHSA-f3px-f8h2-fm4c
• https://sourceforge.net/p/veracrypt/discussion/general/thread/57f938df8b/
• https://github.com/veracrypt/VeraCrypt/issues/1779
• https://github.com/veracrypt/VeraCrypt/issues/1845

Original description

VeraCrypt 1.26.29 (FUSE-T build) on macOS sometimes allows unintended access to decrypted data. It does not terminate the FUSE-T auxiliary service (go-nfsv4) and its associated VeraCrypt core-service helper processes when a volume is dismounted. After VeraCrypt reports the volume as dismounted, the auxiliary mount continues to serve the decrypted volume image (volume.dmg) over a loopback SMB session, and the leaked processes retain an open handle to the underlying raw device. A local user or process can therefore remount and access the decrypted volume without the passphrase, e.g., by reopening a previously accessed path (such as through a macOS Open Recent menu) or by attaching volume.dmg from the stale auxiliary mount. (The macFUSE build of VeraCrypt is not affected.)