Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Cryptomator | Cryptomator | < 1.19.1 |
Related Weaknesses (CWE)
References
- https://github.com/cryptomator/cryptomator/releases/tag/1.19.1Release Notes
- https://github.com/cryptomator/cryptomator/security/advisories/GHSA-vv33-h7qx-c2Vendor Advisory
FAQ
What is CVE-2026-32309?
CVE-2026-32309 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 e...
How severe is CVE-2026-32309?
CVE-2026-32309 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-32309?
Check the references section above for vendor advisories and patch information. Affected products include: Cryptomator Cryptomator.