CVE-2026-108982

Vulnerability record

  • High 7.2

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.)

Key facts

Published
12 Oct 2026
Last changed
15 Oct 2026
Assigned by
mitre
EPSS
0.19% likely to be exploited in the next 30 days, higher than 8.67% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.2CVSS 4.0, Highfrom the CNA (mitre)CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

What to do

  • No fixed release as of 2026-10-11. A community fix exists as VeraCrypt pull request #1866 (commit 000bcf4): on dismount, explicitly shut down the auxiliary FUSE-T service through an authenticated control endpoint and wait for it to terminate before reporting the dismount as complete. The maintainer described the same approach in issue #1779. The macFUSE build of VeraCrypt is unaffected.CNA solution statement
  • Use the macFUSE build of VeraCrypt instead of the FUSE-T build (the maintainer's recommended interim mitigation; the macFUSE build is not affected). If staying on the FUSE-T build: After dismounting your volumes, restart macOS to end any surviving sessions. Using the affected FUSE-T build again can recreate the problem. Updating FUSE-T alone hasn't been verified as a fix. A process name match can't reliably identify every surviving VeraCrypt service. Manual process killing shouldn't be treated as proof that access has ended, and killing a service while a volume is still mounted can interrupt writes.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
IDRIXVeraCrypt
  • Default status: unknown
  • 1.26.29 (affected)

Timeline

  1. 12 Oct 2026 Published

Weakness

References