CVE-2026-32310 | cryptomator up to 1.19.0 Masterkeyfile Loader keyId.getSchemeSpecificPart path traversal (GHSA-5phc-5pfx-hr52)
VulDBArchived Mar 21, 2026✓ Full text saved
A vulnerability was found in cryptomator up to 1.19.0 . It has been rated as critical . This vulnerability affects the function keyId.getSchemeSpecificPart of the component Masterkeyfile Loader . This manipulation causes path traversal. This vulnerability is registered as CVE-2026-32310 . Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352136 · CVE-2026-32310 · GHSA-5PHC-5PFX-HR52
CRYPTOMATOR UP TO 1.19.0 MASTERKEYFILE LOADER KEYID.GETSCHEMESPECIFICPART PATH TRAVERSAL
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.1 $0-$5k 1.64+
Summaryinfo
A vulnerability categorized as critical has been discovered in cryptomator up to 1.19.0. This issue affects the function keyId.getSchemeSpecificPart of the component Masterkeyfile Loader. Such manipulation leads to path traversal. This vulnerability is documented as CVE-2026-32310. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Detailsinfo
A vulnerability, which was classified as critical, has been found in cryptomator up to 1.19.0. Affected by this issue is the function keyId.getSchemeSpecificPart of the component Masterkeyfile Loader. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. CVE summarizes:
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.
The weakness was released by The Master as GHSA-5phc-5pfx-hr52. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-32310 since 03/11/2026. The exploitation is known to be easy. The attack may be launched remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1006.
Upgrading to version 1.6.0 or 1.19.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 1e3dfe3de1623b1b85d24db91e49d31d1ea11f40 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Productinfo
Name
cryptomator
Version
1.0
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
1.11
1.12
1.13
1.14
1.15
1.16
1.17
1.18
1.19.0
License
open-source
Website
Product: https://github.com/cryptomator/cryptomator/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.2
VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.1
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Path traversal
CWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: cryptomator 1.6.0/1.19.1
Patch: 1e3dfe3de1623b1b85d24db91e49d31d1ea11f40
Timelineinfo
03/11/2026 CVE reserved
03/20/2026 +9 days Advisory disclosed
03/20/2026 +0 days VulDB entry created
03/20/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: GHSA-5phc-5pfx-hr52
Researcher: The Master
Status: Confirmed
CVE: CVE-2026-32310 (🔒)
GCVE (CVE): GCVE-0-2026-32310
GCVE (VulDB): GCVE-100-352136
Entryinfo
Created: 03/20/2026 23:31
Changes: 03/20/2026 23:31 (69)
Complete: 🔍
Cache ID: 99:52A:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸