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.
Metrics
Affected Vendors & Products
References
History
Fri, 20 Mar 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes | |
| Weaknesses | CWE-319 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-20T18:19:09.746Z
Reserved: 2026-03-11T21:16:21.659Z
Link: CVE-2026-32309
No data.
Status : Received
Published: 2026-03-20T19:16:15.733
Modified: 2026-03-20T19:16:15.733
Link: CVE-2026-32309
No data.
OpenCVE Enrichment
No data.