CVE-2026-323037.6HighCWE-346

CVE-2026-32303: Cryptomator: Tampered vault configuration allows MITM attack on Hub API

cryptomator

Affected: cryptomator · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.1%probability of exploitation in the next 30 days

1st percentile

050100

Higher than 1% of scored CVEs

7.6HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

cryptomator · cryptomator< 1.19.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Origin Validation Error · Access Control
Vendor: cryptomator
Published: March 2026
Band: Unlikely (under 1%), March 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-32303 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.