CVE-2026-32309

Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes

CVSS 8.7 HIGHEPSS 0.2%CWE-319

Vexday Risk Score

21Low

SSVC decision (CISA)

Track

No exploitation signal → monitor

CVSS 8.7EPSS 0.2%KEV nãoPoC —Nuclei —Metasploit —Patch —

Lifecycle

20 Mar 2026Published on NVD

Recommendation: Monitor — no exploitation signal at the moment.

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

Affected products

cryptomator · cryptomator

Want to know if your infrastructure is exposed to this?

Talk to TrueHacking →

References

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