CVE-2026-32310

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2026-32310
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-32310.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-32310
Aliases
  • GHSA-5phc-5pfx-hr52
Published
2026-03-20T18:19:30.985Z
Modified
2026-04-10T05:42:22.361758Z
Severity
  • 4.1 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N CVSS Calculator
Summary
Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths
Details

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.

Database specific 
{
    "cwe_ids": [
        "CWE-22"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/32xxx/CVE-2026-32310.json",
    "cna_assigner": "GitHub_M"
}
References

Affected packages

Git / github.com/cryptomator/cryptomator

Affected ranges

Type
GIT
Repo
https://github.com/cryptomator/cryptomator
Events
Introduced
1daab1a4f14403f63925fe08704580d99c362e7b
Fixed
1e3dfe3de1623b1b85d24db91e49d31d1ea11f40

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-32310.json"