Read the docs
TI-2026-24838 Aliases CVE-2026-32310

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

Priority MEDIUM 57CWE-22Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
Low · None · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-22 and the CVSS impact.

Summary

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00263 18th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
cryptomatorcryptomator1.6.0 – 1.19.0—No fix listedCNA
  • cryptomator Vendorcryptomator Affected 1.6.0 – 1.19.0 Fixed in — No fix listed CNA

CPE configurations NVD · 2

CPEVersionsRoleVendor
cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*1.6.0 – 1.19.0Vulnerablecryptomator
cpe:2.3:o:microsoft:windows:*:*:*:*:*:*:*:*all versionsRunning onMicrosoft
  • cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:* Versions 1.6.0 – 1.19.0 Vulnerable ·cryptomator
  • cpe:2.3:o:microsoft:windows:*:*:*:*:*:*:*:* Versions all versions Running on ·Microsoft

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-32310

References

Patch 1

Advisory 1

Other 2

  • TI-2023-19340 Cryptomator's MSI installer allows local privilege escalation CVSS 3.1HIGH 7.8
  • TI-2023-20652 Cryptomator vulnerable to Local Elevation of Privileges CVSS 3.1HIGH 7.8
  • TI-2026-25868 Cryptomator Hub OAuth token exchange HTTP downgrade via getAuthority() scheme confusion (CVE-2026-32303 bypass) CVSS 3.1MEDIUM 4.8
  • TI-2026-24837 Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes CVSS 4.0HIGH 8.7
  • TI-2022-09052 Cryptomator through 1.6.5 allows DYLIB injection because, although it has the flag 0x1000… CVSS 3.1HIGH 7.8
  • TI-2026-24846 Cryptomator for IOS: Tampered vault configuration allows MITM attack on Hub API CVSS 3.1HIGH 7.6
See all 9 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences