How severe is CVE-2026-32309?

CVE-2026-32309 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-32309 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-32309?

CVE-2026-32309 affects Cryptomator. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-32309?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-32309 have an EU (EUVD) identifier?

Yes. CVE-2026-32309 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-13748.

When was CVE-2026-32309 published?

CVE-2026-32309 was published on 2026-03-20 and last updated on 2026-06-17.

CVE-2026-32309

CVE-2026-32309 is a high-severity vulnerability in Cryptomator with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-319.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v4: 8.7
EPSS exploit prediction: 0% (10th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-13748
Weakness: CWE-319
Affected product: Cryptomator
Published: 2026-03-20
Last modified: 2026-06-17

Description

Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, the Hub-based unlock flow explicitly supports hub+http and consumes Hub endpoints from vault metadata without enforcing HTTPS. As a result, a vault configuration can drive OAuth and key-loading traffic over plaintext HTTP or other insecure endpoint combinations. An active network attacker can tamper with or observe this traffic. Even when the vault key is encrypted for the device, bearer tokens and endpoint-level trust decisions are still exposed to downgrade and interception. This issue has been patched in version 1.19.1.

Frequently asked questions

What is CVE-2026-32309?: Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, the Hub-based unlock flow explicitly supports hub+http and consumes Hub endpoints from vault metadata without enforcing HTTPS. As a result, a vault configuration can drive OAuth and key-loading traffic over plaintext HTTP or other insecure endpoint combinations. An active network attacker can tamper with or observe this traffic. Even when the vault key is encrypted for the device, bearer tokens and endpoint-level trust decisions are still exposed to downgrade and interception. This issue has been patched in version 1.19.1.
How severe is CVE-2026-32309?: CVE-2026-32309 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-32309 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-32309?: CVE-2026-32309 affects Cryptomator. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-32309?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-32309 have an EU (EUVD) identifier?: Yes. CVE-2026-32309 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-13748.
When was CVE-2026-32309 published?: CVE-2026-32309 was published on 2026-03-20 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*

More vulnerabilities in Cryptomator

CVE-2022-25366 — High (CVSS 7.8): Cryptomator through 1.6.5 allows DYLIB injection because, although it has the flag 0x1000 for Hardened Runtime, it has…
CVE-2026-32318 — High (CVSS 7.6): Cryptomator for IOS offers multi-platform transparent client-side encryption for files in the cloud. Prior to version…
CVE-2026-32317 — High (CVSS 7.6): Cryptomator for Android offers multi-platform transparent client-side encryption for files in the cloud. Prior to…
CVE-2026-32303 — High (CVSS 7.6): Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, an integrity check…
CVE-2023-37907 — High (CVSS 7.0): Cryptomator is data encryption software for users who store their files in the cloud. Prior to version 1.9.2, the MSI…
CVE-2023-39520 — Medium (CVSS 5.5): Cryptomator encrypts data being stored on cloud infrastructure. The MSI installer provided on the homepage for…

All CVEs affecting Cryptomator →

Other CWE-319 (Cleartext Transmission of Sensitive Information) vulnerabilities

CVE-2025-4378 — Critical (CVSS 10.0): Cleartext Transmission of Sensitive Information, Use of Hard-coded Credentials vulnerability in Ataturk University…
CVE-2025-47419 — Critical (CVSS 10.0): Cleartext Transmission of Sensitive Information vulnerability in Crestron Automate VX allows Sniffing Network…
CVE-2026-48902 — Critical (CVSS 9.8): The password and username reset features created plain http links for https connections if the "Force SSL" flag wasn't…
CVE-2025-34271 — Critical (CVSS 9.8): Nagios Log Server versions prior to 2024R2.0.2 contain a vulnerability in the cluster manager component when…
CVE-2025-32880 — Critical (CVSS 9.8): An issue was discovered on COROS PACE 3 devices through 3.0808.0. It implements a function to connect the watch to a…
CVE-2025-26199 — Critical (CVSS 9.8): CloudClassroom-PHP-Project v1.0 is affected by an insecure credential transmission vulnerability. The application…

Browse all CWE-319 (Cleartext Transmission of Sensitive Information) vulnerabilities →