CVE-2026-32303
Cryptomator encrypts data being stored on cloud infrastructure. …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/cryptomator/cryptomator/commit/6b82abcd80449a30b561d823193f9ecea542a625
- github.com/cryptomator/cryptomator/pull/4179
- github.com/cryptomator/cryptomator/releases/tag/1.19.1
- github.com/cryptomator/cryptomator/security/advisories/GHSA-34rf-rwr3-7g43
- nvd.nist.gov/vuln/detail/CVE-2026-32303
- cve.org/CVERecord?id=CVE-2026-32303
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.