CVE-2026-32309: fallo de gravedad alta en cryptomator
Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 8.7epss 0.2%
Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, the Hub-based unlock flow explicitly supports hub+http and consumes Hub endpoints from vault metadata without enforcing HTTPS. As a result, a vault configuration can drive OAuth and key-loading traffic over plaintext HTTP or other insecure endpoint combinations. An active network attacker can tamper with or observe this traffic. Even when the vault key is encrypted for the device, bearer tokens and endpoint-level trust decisions are still exposed to downgrade and interception. This issue has been patched in version 1.19.1.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Productos afectados
cryptomator · cryptomatorCVEs relacionadas — cryptomator
En el mismo producto, de las más peligrosas a las menos.
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-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-32303HIGHCryptomator: Tampered vault configuration allows MITM attack on Hub APIEPSS 0.1%CVE-2026-33472MEDIUMCryptomator Hub OAuth token exchange HTTP downgrade via getAuthority() scheme confusion (CVE-2026-32303 bypass)EPSS 0.1%