CVE-2026-32310

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

Configuration 1 (hide)

AND
cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows:*:*:*:*:*:*:*:*

History

25 Mar 2026, 20:45

Type Values Removed Values Added
References () https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40 - () https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40 - Patch
References () https://github.com/cryptomator/cryptomator/pull/4180 - () https://github.com/cryptomator/cryptomator/pull/4180 - Issue Tracking
References () https://github.com/cryptomator/cryptomator/releases/tag/1.19.1 - () https://github.com/cryptomator/cryptomator/releases/tag/1.19.1 - Release Notes
References () https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52 - () https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52 - Vendor Advisory, Mitigation
Summary
  • (es) Cryptomator cifra datos almacenados en infraestructura en la nube. Desde la versión 1.6.0 hasta antes de la versión 1.19.1, la configuración de la bóveda se analiza antes de que se verifique su integridad, y el cargador de masterkeyfile utiliza el keyId no verificado como una ruta del sistema de archivos. El cargador resuelve keyId.getSchemeSpecificPart() directamente contra la ruta de la bóveda e inmediatamente llama a Files.exists(...). Esto permite a una configuración de bóveda maliciosa proporcionar escapes de directorio padre, rutas locales absolutas o rutas UNC (p. ej., masterkeyfile://atacante/share/masterkey.cryptomator). En Windows, la variante UNC es especialmente peligrosa porque Path.resolve("//atacante/share/...") se convierte en \\atacante\share\..., por lo que la verificación de existencia puede activar el acceso SMB saliente antes de que el usuario siquiera introduzca una frase de contraseña. Este problema ha sido parcheado en la versión 1.19.1.
CPE cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows:*:*:*:*:*:*:*:*
First Time Cryptomator cryptomator
Cryptomator
Microsoft
Microsoft windows

20 Mar 2026, 19:16

Type Values Removed Values Added
New CVE

Information

Published : 2026-03-20 19:16

Updated : 2026-03-25 20:45


NVD link : CVE-2026-32310

Mitre link : CVE-2026-32310

CVE.ORG link : CVE-2026-32310


JSON object : View

Products Affected

microsoft

  • windows

cryptomator

  • cryptomator
CWE
CWE-22

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