Path Traversal in Cryptomator

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.

Vulnerability class: Path Traversal (Directory Traversal)

Published · last modified .

CVSS v3 metric

CVSS v3 base score 4.1 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N.

EPSS exploit prediction

EPSS: 0.004 (27.2th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 27th percentile — 27.2% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-32310: held from 0.002 to 0.004.

EPSS over last 30 days · oldest: 0.002 · newest: 0.004 · change: +0.001

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-32310?
CVE-2026-32310 is a medium-severity vulnerability in Cryptomator, classified under Path Traversal. CVSS score: 4.1/10. Published 2026-03-20.
How severe is CVE-2026-32310?
Medium severity. CVSS v3 base score is 4.1 out of 10.