CVE-2026-32309

Published: Mar 20, 2026 Last Modified: Mar 20, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 8,7
Source: [email protected]
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: passive
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation Available

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.

319

Cleartext Transmission of Sensitive Information

Draft
Abstraction: Base Structure: Simple
Common Consequences
Security Scopes Affected:
Integrity Confidentiality
Potential Impacts:
Read Application Data Modify Files Or Directories Other
Applicable Platforms
Technologies: Cloud Computing, ICS/OT, Mobile, Not Technology-Specific, System on Chip, Test/Debug Hardware
Likelihood of Exploit: High
View CWE Details
https://github.com/cryptomator/cryptomator/releases/tag/1.1…
https://github.com/cryptomator/cryptomator/releases/tag/1.19.1
https://github.com/cryptomator/cryptomator/security/advisor…
https://github.com/cryptomator/cryptomator/security/advisories/GHSA-vv33-h7qx-c…