CVE-2026-32310

Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths

Published Mar 20, 2026 CVSS 3.1 · 4.1 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Cryptomator encrypts cloud data through vaults, but from version 1.6.0 to just before 1.19.1 the system parses the vault configuration before checking its integrity. The masterkeyfile loader treats the keyId supplied in the configuration as a file‑system path without validation. An attacker can insert parent‑directory escapes or absolute paths – for example using a masterkeyfile://prefix that resolves to a UNC share – so the application will call the path existence check before any password is entered. This can allow reading of arbitrary local files or triggering outbound SMB requests to attacker controlled shares, potentially exposing sensitive data.

Affected Systems

Cryptomator versions 1.6.0 through 1.19.0 on any platform detected by the CPE – particularly Windows, where UNC resolution is risky. The vulnerability does not affect earlier versions or 1.19.1 and later. The affected software is the Cryptomator desktop application distributed by the vendor cryptomator:cryptomator. Windows operating systems are especially relevant because of the SMB path resolution.

Risk and Exploitability

The CVSS score of 4.1 reflects moderate risk; the EPSS score shows less than 1% probability of exploitation today, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation requires a user to load or open a vault whose configuration contains a malicious masterkeyfile keyId, which the attacker can supply via a compromised cloud folder or a phishing attachment. Once the vault is opened, the existence check for the supplied path occurs before the user enters the vault password, so the exploit can succeed without further interaction. Consequently, the main risk is local or network file disclosure rather than remote code execution.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Cryptomator to version 1.19.1 or later.
  • Verify that all vault configuration files originate from trusted sources and remove or correct any that use arbitrary masterkeyfile paths.

Generated by OpenCVE AI on March 25, 2026 at 23:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Microsoft
Microsoft windows
CPEs cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows:*:*:*:*:*:*:*:*
Vendors & Products Microsoft
Microsoft windows
Type Values Removed Values Added
First Time appeared Cryptomator
Cryptomator cryptomator
Vendors & Products Cryptomator
Cryptomator cryptomator
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths
Weaknesses CWE-22
References
Metrics cvssV3_1

{'score': 4.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 20, 2026, 7:56 PM
Reserved
Mar 11, 2026, 9:16 PM
Status
Analyzed
Published
Mar 20, 2026, 7:16 PM
Modified
Jun 17, 2026, 10:35 AM