CVE-2026-32310 Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
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.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| cryptomator | = >= 1.6.0, <= 1.19.0; >= 1.6.0, <= 1.19.0 | after 1.19.0 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| cryptomator | = >= 1.6.0, <= 1.19.0 | No fix listed |
| cryptomator | >= 1.6.0, <= 1.19.0 | No fix listed |
References
- https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52 mitigation vendor-advisory
- https://github.com/cryptomator/cryptomator/pull/4180 issue-tracking
- https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40 patch
- https://github.com/cryptomator/cryptomator/releases/tag/1.19.1 release-notes