PT-2026-26657 · Cryptomator · Cryptomator

Yanchon918S · Published 2026-03-20 · Updated 2026-03-20 · CVE-2026-32309

NVD

CVSS v4.0

8.7

High

AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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.

Fix

Cleartext Transmission of Sensitive Information

Weakness Enumeration

CWE-319

Related Identifiers

CVE-2026-32309

Affected Products

Cryptomator

References · 3

• https://nvd.nist.gov/vuln/detail/CVE-2026-32309 · Security Note
• https://github.com/cryptomator/cryptomator/releases/tag/1.19.1 · Note
• https://github.com/cryptomator/cryptomator/security/advisories/GHSA-vv33-h7qx-c264 · Note