CVE-2026-32303: high-severity vulnerability in cryptomator
Cryptomator: Tampered vault configuration allows MITM attack on Hub API
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.6epss 0.1%
Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, an integrity check vulnerability allows an attacker to tamper with the vault configuration file leading to a man-in-the-middle vulnerability in Hub key loading mechanism. Before this fix, the client trusted endpoints from the vault config without host authenticity checks, which could allow token exfiltration by mixing a legitimate auth endpoint with a malicious API endpoint. Impacted are users unlocking Hub-backed vaults with affected client versions in environments where an attacker can alter the vault.cryptomator file. This issue has been patched in version 1.19.1.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
Affected products
cryptomator · cryptomatorRelated CVEs — cryptomator
In the same product, most dangerous first.
CVE-2023-39520MEDIUMCryptomator vulnerable to Local Elevation of PrivilegesEPSS 0.3%CVE-2026-32310MEDIUMCryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC pathsEPSS 0.3%CVE-2026-32309HIGHCryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemesEPSS 0.2%CVE-2023-37907HIGHCryptomator's MSI installer allows local privilege escalationEPSS 0.2%CVE-2026-29110LOWCryptomator: Leaking of cleartext paths into log file in non-debug modeEPSS 0.1%CVE-2026-33472MEDIUMCryptomator Hub OAuth token exchange HTTP downgrade via getAuthority() scheme confusion (CVE-2026-32303 bypass)EPSS 0.1%