CVE-2026-32309 HIGH

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

Vendor Cryptomator
Product cryptomator
Weakness CWE-319 · Cleartext transmission
Published March 20, 2026
Last update March 27, 2026

CVSS base score

8.7/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction
Confidentiality
Integrity

CVSS 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

What the vulnerability does

01Description

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.

Key dates

02Disclosure timeline

March 20, 2026 CVE published
March 27, 2026 Record updated