CVE-2026-32310

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.
Configurations

Configuration 1 (hide)

AND
cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows:*:*:*:*:*:*:*:*

History

No history.

Information

Published : 2026-03-20 19:16

Updated : 2026-03-25 20:45


NVD link : CVE-2026-32310

Mitre link : CVE-2026-32310

CVE.ORG link : CVE-2026-32310


JSON object : View

Products Affected

microsoft

  • windows

cryptomator

  • cryptomator
CWE
CWE-22

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')