CVE-2026-32309

UNKNOWN 0.0

Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes

CVSS Score

0.0

EPSS Score

0.0%

EPSS Percentile

5th

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.

CWE	CWE-319
Vendor	cryptomator
Product	cryptomator
Published	Mar 20, 2026
Last Updated	Mar 27, 2026

Stay Ahead of the Next One

Get instant alerts for cryptomator cryptomator

Be the first to know when new unknown vulnerabilities affecting cryptomator cryptomator are published — delivered to Slack, Telegram or Discord.

Get Free Alerts → Free · No credit card · 60 sec setup

Affected Versions

cryptomator / cryptomator

< 1.19.1

References

NVD ↗ CVE.org ↗ EPSS Data ↗

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