CVE-2026-32310
Cryptomator encrypts data being stored on cloud infrastructure. …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40
- github.com/cryptomator/cryptomator/pull/4180
- github.com/cryptomator/cryptomator/releases/tag/1.19.1
- github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52
- nvd.nist.gov/vuln/detail/CVE-2026-32310
- cve.org/CVERecord?id=CVE-2026-32310
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.