What’s Vulnerable › Vulnerabilities

CVE-2026-32310: Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths

• Severity: medium (CVSS 5.3 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.3% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-03-20 · updated 2026-06-17
• Weakness: CWE-22

Description

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.

Affected products

• cryptomator: from 1.6.0 through 1.19.0

References

• https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40
• https://github.com/cryptomator/cryptomator/pull/4180
• https://github.com/cryptomator/cryptomator/releases/tag/1.19.1
• https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52

Get alerted when CVE-2026-32310 or the next vulnerability affects your stack