{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-108982","assignerOrgId":"8254265b-2729-46b6-b9e3-3dfca2d5bfca","state":"PUBLISHED","assignerShortName":"mitre","dateReserved":"2026-10-12T02:44:03.885Z","datePublished":"2026-10-12T02:44:04.730Z","dateUpdated":"2026-10-15T02:49:02.840Z"},"containers":{"cna":{"affected":[{"defaultStatus":"unknown","modules":["FUSE-T build for macOS: auxiliary FUSE-T mount and dismount handling (FuseService)"],"platforms":["MacOS"],"product":"VeraCrypt","programFiles":["src/Driver/Fuse/FuseService.cpp"],"repo":"https://github.com/veracrypt/VeraCrypt","vendor":"IDRIX","versions":[{"status":"affected","version":"1.26.29","versionType":"semver"}]}],"descriptions":[{"lang":"en","value":"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.)"}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"PRESENT","attackVector":"LOCAL","baseScore":7.2,"baseSeverity":"HIGH","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"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","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-459","description":"CWE-459 Incomplete Cleanup","lang":"en","type":"CWE"}]}],"providerMetadata":{"orgId":"8254265b-2729-46b6-b9e3-3dfca2d5bfca","shortName":"mitre","dateUpdated":"2026-10-15T02:49:02.840Z"},"references":[{"name":"Original public report (June 2026) with maintainer acknowledgment and diagnosis","url":"https://github.com/veracrypt/VeraCrypt/issues/1779"},{"name":"Independent report with first process-level diagnosis and maintainer reply (June 2026)","url":"https://sourceforge.net/p/veracrypt/discussion/general/thread/57f938df8b/"},{"name":"Consolidated issue: reproductions, lsof evidence, kernel panic analysis, status","url":"https://github.com/veracrypt/VeraCrypt/issues/1845"},{"name":"Community fix: terminate auxiliary FUSE-T service on dismount","url":"https://github.com/veracrypt/VeraCrypt/pull/1866"},{"name":"Affected release 1.26.29","tags":["product"],"url":"https://github.com/veracrypt/VeraCrypt/releases/tag/VeraCrypt_1.26.29"},{"url":"https://github.com/veracrypt/VeraCrypt/security/advisories/GHSA-f3px-f8h2-fm4c"},{"url":"https://github.com/veracrypt/VeraCrypt/commit/d7bc65bed004996d299ec76666d1b283a07e2526"}],"solutions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"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."}],"value":"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."}],"workarounds":[{"lang":"en","value":"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."}],"x_generator":{"engine":"CVE-Request-form 0.0.1"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:idrix:veracrypt:*:*:*:*:*:*:*:*","versionStartIncluding":"1.26.29","versionEndIncluding":"1.26.29"}]}]}]},"adp":[{"references":[{"url":"https://github.com/veracrypt/VeraCrypt/issues/1779","tags":["exploit"]},{"url":"https://github.com/veracrypt/VeraCrypt/issues/1845","tags":["exploit"]}],"metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-10-13T18:25:54.498453Z","id":"CVE-2026-108982","options":[{"Exploitation":"poc"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"title":"CISA ADP Vulnrichment","providerMetadata":{"orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP","dateUpdated":"2026-10-13T18:26:02.840Z"}}]}}