What’s Vulnerable › Vulnerabilities

CVE-2026-32309: Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes

• Severity: high (CVSS 7.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-03-20 · updated 2026-06-17
• Weakness: CWE-319

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

• cryptomator: before 1.19.1 — fixed in 1.19.1

How to fix

Upgrade to a fixed version: cryptomator 1.19.1. Check the vendor advisory for mitigations.

References

• https://github.com/cryptomator/cryptomator/releases/tag/1.19.1
• https://github.com/cryptomator/cryptomator/security/advisories/GHSA-vv33-h7qx-c264

Get alerted when CVE-2026-32309 or the next vulnerability affects your stack