# 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.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N`)
- **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 available:** No
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-5phc-5pfx-hr52

## 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 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-32310?

It affects 1 product.


Products: 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.

## 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](https://insights.sbomify.com/CVE-2026-32309/): Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes (high 8.7)
- [CVE-2022-25366](https://insights.sbomify.com/CVE-2022-25366/): Code injection in n/a (high 7.8)
- [CVE-2026-32303](https://insights.sbomify.com/CVE-2026-32303/): Cryptomator: Tampered vault configuration allows MITM attack on Hub API (high 7.6)
- [CVE-2026-32317](https://insights.sbomify.com/CVE-2026-32317/): Cryptomator for Android: Tampered vault configuration allows MITM attack on Hub API (high 7.6)
- [CVE-2026-32318](https://insights.sbomify.com/CVE-2026-32318/): Cryptomator for IOS: Tampered vault configuration allows MITM attack on Hub API (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32310 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32310 exists.

Affected product: cryptomator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32310/ (Markdown: https://insights.sbomify.com/CVE-2026-32310/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32310
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32310
- OSV: https://osv.dev/vulnerability/CVE-2026-32310

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32310/
Summaries are generated and may contain mistakes; the official description above is the record.