{
    "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-12T02:44:04.730Z"
    },
    "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/Core/Unix/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-12T02:44:04.730Z"
            },
            "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"
                }
            ],
            "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",
                    "supportingMedia": [
                        {
                            "base64": false,
                            "type": "text/html",
                            "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 every dismount, and only when no volumes are mounted, kill the leaked processes so the decrypted volume and the raw device are actually released: sudo pkill -9 -f 'go-nfsv4.*veracrypt_aux_mnt' and sudo pkill -9 -f 'VeraCrypt.*--core-service' (the processes ignore SIGTERM). Do this before sleeping the machine to avoid the kernel panic when the volume is on removable media. Scope the pkill patterns as shown; an unscoped match also kills other FUSE-T applications' servers. A reboot is the only fully verified lockdown."
                        }
                    ],
                    "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 every dismount, and only when no volumes are mounted, kill the leaked processes so the decrypted volume and the raw device are actually released: sudo pkill -9 -f 'go-nfsv4.*veracrypt_aux_mnt' and sudo pkill -9 -f 'VeraCrypt.*--core-service' (the processes ignore SIGTERM). Do this before sleeping the machine to avoid the kernel panic when the volume is on removable media. Scope the pkill patterns as shown; an unscoped match also kills other FUSE-T applications' servers. A reboot is the only fully verified lockdown."
                }
            ],
            "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"
                                }
                            ]
                        }
                    ]
                }
            ]
        }
    }
}