Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths
Cryptomator encrypts data being stored on cloud infrastructure. From version 1.6.0 to before version 1.19.1, vault configuration is parsed before its integrity is verified, and the masterkeyfile loader uses the unverified keyId as a filesystem path. The loader resolves keyId.getSchemeSpecificPart() directly against the vault path and immediately calls Files.exists(...). This allows a malicious vault config to supply parent-directory escapes, absolute local paths, or UNC paths (e.g., masterkeyfile://attacker/share/masterkey.cryptomator). On Windows, the UNC variant is especially dangerous because Path.resolve("//attacker/share/...") becomes \\attacker\share\..., so the existence check can trigger outbound SMB access before the user even enters a passphrase. This issue has been patched in version 1.19.1.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-32310
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 03:36 UTC · Revision 1
Source evidence
Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths
core-osv · Original sourcePublished 20 Mar 2026, 18:19 UTC
Cryptomator encrypts data being stored on cloud infrastructure. From version 1.6.0 to before version 1.19.1, vault configuration is parsed before its integrity is verified, and the masterkeyfile loader uses the unverified keyId as a filesystem path. The loader resolves keyId.getSchemeSpecificPart() directly against the vault path and immediately calls Files.exists(...). This allows a malicious vault config to supply parent-directory escapes, absolute local paths, or UNC paths (e.g., masterkeyfile://attacker/share/masterkey.cryptomator). On Windows, the UNC variant is especially dangerous because Path.resolve("//attacker/share/...") becomes \\attacker\share\..., so the existence check can trigger outbound SMB access before the user even enters a passphrase. This issue has been patched in version 1.19.1.
osv:CVE-2026-32310
Complete source record
{
"id": "ba9568a6e0b083b19e02224ed5835b13a0e654602e7a857cd65368af11a304ca",
"url": "https://osv.dev/vulnerability/CVE-2026-32310",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths",
"summary": "Cryptomator encrypts data being stored on cloud infrastructure. From version 1.6.0 to before version 1.19.1, vault configuration is parsed before its integrity is verified, and the masterkeyfile loader uses the unverified keyId as a filesystem path. The loader resolves keyId.getSchemeSpecificPart() directly against the vault path and immediately calls Files.exists(...). This allows a malicious vault config to supply parent-directory escapes, absolute local paths, or UNC paths (e.g., masterkeyfile://attacker/share/masterkey.cryptomator). On Windows, the UNC variant is especially dangerous because Path.resolve(\"//attacker/share/...\") becomes \\\\attacker\\share\\..., so the existence check can trigger outbound SMB access before the user even enters a passphrase. This issue has been patched in version 1.19.1.",
"evidence": "osv:CVE-2026-32310",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-32310",
"aliases": [
"CVE-2026-32310",
"GHSA-5phc-5pfx-hr52"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/cryptomator/cryptomator",
"type": "GIT",
"events": [
{
"introduced": "1daab1a4f14403f63925fe08704580d99c362e7b"
},
{
"fixed": "1e3dfe3de1623b1b85d24db91e49d31d1ea11f40"
},
{
"fixed": "4be327608a6d478d5d9055121f0ab28fd649b864"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "1.6.0"
},
{
"last_affected": "1.19.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "1e3dfe3de1623b1b85d24db91e49d31d1ea11f40"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "4be327608a6d478d5d9055121f0ab28fd649b864"
}
],
"source": "REFERENCES_TAG",
"original_tag": "1.19.1"
}
]
}
}
],
"versions": [
"1.19.0",
"1.18.1",
"1.18.0",
"1.17.1",
"1.17.0",
"1.16.2",
"1.16.1",
"1.16.0",
"1.15.3",
"1.15.2",
"1.15.1",
"1.15.0",
"1.14.2",
"1.14.1",
"1.14.0",
"1.13.0",
"1.12.4",
"1.12.3",
"1.12.2",
"1.12.1",
"1.12.0",
"1.11.1",
"1.11.0",
"1.10.1",
"1.10.0",
"1.9.4",
"1.9.3",
"1.9.2",
"1.9.1",
"1.9.0",
"1.8.0",
"1.7.5",
"1.7.4",
"1.7.3",
"1.7.2",
"1.7.1",
"1.7.0",
"1.6.17",
"1.6.16",
"1.6.15",
"1.6.14",
"1.6.13",
"1.6.12",
"1.6.11",
"1.6.10",
"1.6.9",
"1.6.8",
"1.6.7",
"1.6.6",
"1.6.5",
"1.6.4",
"1.6.3",
"1.6.2",
"1.6.1",
"1.6.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-32310.json"
}
}
],
"modified": "2026-10-28T02:30:49.627514915Z",
"provider": "osv",
"references": [
"https://github.com/cryptomator/cryptomator/releases/tag/1.19.1",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/32xxx/CVE-2026-32310.json",
"https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52",
"https://nvd.nist.gov/vuln/detail/CVE-2026-32310",
"https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40",
"https://github.com/cryptomator/cryptomator/pull/4180"
],
"provider_metadata": {
"cwe_ids": [
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/32xxx/CVE-2026-32310.json"
}
},
"related_cves": [
{
"value": "CVE-2026-32310",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517806,
"published_at": "2026-03-20T18:19:30.985+00:00"
}