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.
INFO
Published Date :
2026-03-20T18:19:30.985Z
Last Modified :
2026-03-20T19:56:38.604Z
Source :
GitHub_M
AFFECTED PRODUCTS
The following products are affected by CVE-2026-32310 vulnerability.
| Vendors | Products |
|---|---|
| Cryptomator |
|
| Microsoft |
|
REFERENCES
Here, you will find a curated list of external links that provide in-depth information to CVE-2026-32310.
