{
  "id": "CVE-2026-108982",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-108982",
  "published_at": "2026-10-12T02:44:04.73Z",
  "vendor": "IDRIX",
  "product": "VeraCrypt",
  "cvss": {
    "score": 7.2,
    "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.)",
  "cwe": "CWE-459",
  "cvss_by_source": {
    "cna": 7.2
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "IDRIX",
        "product": "VeraCrypt",
        "ranges": [
          "1.26.29"
        ],
        "fixed_in": null
      }
    ],
    "solutions": [
      "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": [
      "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."
    ],
    "references": [
      {
        "kind": "Patch",
        "url": "https://github.com/veracrypt/VeraCrypt/pull/1866"
      },
      {
        "kind": "Release notes",
        "url": "https://github.com/veracrypt/VeraCrypt/releases/tag/VeraCrypt_1.26.29"
      },
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/veracrypt/VeraCrypt/security/advisories/GHSA-f3px-f8h2-fm4c"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/veracrypt/VeraCrypt/commit/d7bc65bed004996d299ec76666d1b283a07e2526"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
