Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
| Date | Total | Labels |
|---|
| 2026-03-22 | 1 | Disclosure1 |
| 2026-03-26 | 1 | General1 |
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 … https://www.cve.org/CVERecord?id=CVE-2026-32303
Post summary
An integrity‑check flaw in Cryptomator prior to version 1.19.1 allows attackers to tamper with vault data stored on cloud infrastructure.
CVE-2026-32303: Cryptomator Vault Configuration Bug - What It Means for Your Business and How to Respond https://hubs.li/Q048t7BC0
Post summary
The fragment only lists the CVE id and a title, offering no information on proof‑of‑concepts, exploitation, or patches.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | cryptomator | cryptomator | - | - | - |