CVE-2026-32310 Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths
A malicious vault configuration can force Cryptomator to access arbitrary local or network paths, potentially leaking data or triggering SMB requests before authentication.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-32310?
CVE-2026-32310 is a medium-severity path traversal vulnerability in cryptomator, published on 20 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-22
Which versions are affected by CVE-2026-32310?
It affects 1 product.
Products include Cryptomator Cryptomator.
How do I fix CVE-2026-32310?
No fix has been published for CVE-2026-32310 yet. Limit exposure of the affected software until one is available.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-32310 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32310 exists.
Other vulnerabilities in cryptomator
- CVE-2026-32309 Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes
- CVE-2022-25366 Code injection in n/a
- CVE-2026-32303 Cryptomator: Tampered vault configuration allows MITM attack on Hub API
- CVE-2026-32317 Cryptomator for Android: Tampered vault configuration allows MITM attack on Hub API
- CVE-2026-32318 Cryptomator for IOS: Tampered vault configuration allows MITM attack on Hub API
Sources
Also known as GHSA-5phc-5pfx-hr52.