{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108982 exists.","fix":"No fix has been published for CVE-2026-108982 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-108982 is a high-severity vulnerability in IDRIX VeraCrypt, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-108982 and fix it if it is affected.\n\nWhat it is: CVE-2026-108982 is a high-severity vulnerability in IDRIX VeraCrypt, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108982 exists.\n\nAffected product: IDRIX VeraCrypt. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-108982/ (Markdown: https://insights.sbomify.com/CVE-2026-108982/index.md)","id":"CVE-2026-108982","markdown":"https://insights.sbomify.com/CVE-2026-108982/index.md","name":"CVE-2026-108982","record":{"aliases":["GHSA-f3px-f8h2-fm4c","GHSA-h6r2-r3xv-333f"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VeraCrypt disk encryption","requires_auth":"low_privilege","summary":"Local attackers can access decrypted data from dismounted VeraCrypt volumes on macOS due to lingering FUSE-T processes retaining open handles.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"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"},"cwes":[{"id":"CWE-459","name":"Incomplete Cleanup"}],"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.)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in VeraCrypt","id":"CVE-2026-108982","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"GV-ASManager Web Server Command Injection Vulnerability","id":"CVE-2026-108983"},"packages":[],"prev":{"headline":"Path traversal in ngx cache purge","id":"CVE-2026-108981"},"products":["VeraCrypt"],"published":"2026-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["IDRIX"]},"summary":"Local attackers can access decrypted data from dismounted VeraCrypt volumes on macOS due to lingering FUSE-T processes retaining open handles.","url":"https://insights.sbomify.com/CVE-2026-108982/"}