Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 26 Mar 2026 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:* |
Tue, 24 Mar 2026 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 23 Mar 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Cryptomator
Cryptomator cryptomator |
|
| Vendors & Products |
Cryptomator
Cryptomator cryptomator |
Fri, 20 Mar 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Cryptomator: Tampered vault configuration allows MITM attack on Hub API | |
| Weaknesses | CWE-346 CWE-354 CWE-451 CWE-923 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-23T21:41:57.420Z
Reserved: 2026-03-11T21:16:21.659Z
Link: CVE-2026-32303
Updated: 2026-03-23T21:32:00.491Z
Status : Analyzed
Published: 2026-03-20T18:16:14.593
Modified: 2026-03-26T13:55:14.187
Link: CVE-2026-32303
No data.
OpenCVE Enrichment
Updated: 2026-03-27T09:21:33Z