Vulnerability · Published Mar 20, 2026 · Assigned by GitHub_M
CVE-2026-32309Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes
High 8.7
In plain English
A high-severity security flaw in cryptomator from cryptomator. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities).
Official 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.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| cryptomator | cryptomator | < 1.19.1 |
Weakness: CWE-319 · Vector: 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
References
- https://github.com/cryptomator/cryptomator/security/advisories/GHSA-vv33-h7qx-c264 x_refsource_CONFIRM
- https://github.com/cryptomator/cryptomator/releases/tag/1.19.1 x_refsource_MISC