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.)
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 3
- StatusReceived → Awaiting AnalysisNVD modified 2026-10-16 17:25
- References+2 references (now 9)NVD modified 2026-10-15 03:17
- First seenCVSS 7.2NVD modified 2026-10-13 19:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 9
- 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