CVE-2026-32303
Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, an integrity check vulnerability allows an attacker to tamper with the vault configuration file leading to a man-in-the-middle vulnerability in Hub key loading mechanism. Before this fix, the client trusted endpoints from the vault config without host authenticity checks, which could allow token exfiltration by mixing a legitimate auth endpoint with a malicious API endpoint. Impacted are users unlocking Hub-backed vaults with affected client versions in environments where an attacker can alter the vault.cryptomator file. This issue has been patched in version 1.19.1.
Scoring
- Severity
- HIGH
- CVSS base score
- 7.6
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
- EPSS probability
- 0.11%
- CWE
- CWE-346, CWE-354, CWE-451, CWE-923
- Published
- 2026-03-20
- Last modified
- 2026-03-23
Affected products
- cryptomator cryptomator
Weakness type
Related vulnerabilities
- CVE-2026-87563 — Origin validation error in Paint in Google Chrome prior to 153.0.8010.36 allowed a remote attacker...
- CVE-2026-58649 — .NET Information Disclosure Vulnerability
- CVE-2026-69559 — Microsoft Teams for Android Information Disclosure Vulnerability
- CVE-2026-69680 — Windows DNS Spoofing Vulnerability
- CVE-2026-75156 — Apache Airflow FAB provider: FAB Azure AD OAuth: id_token issuer/audience not validated — cross-tenant authentication bypass
- CVE-2026-85152 — undici vulnerable to cross-origin cache poisoning via missing origin isolation in interceptors
- CVE-2026-84482 — WWBN AVideo Cross-Site Request Forgery via get_domain() validation
- CVE-2026-82811 — Toggl OÜ Toggl Track Extension postMessage origin validation