CVE-2026-32309 Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes

High 8.7 Published 20 Mar 2026 Updated 27 Mar 2026

An active network attacker can intercept or tamper with Cryptomator Hub authentication traffic due to lack of HTTPS enforcement, exposing bearer tokens.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: A user has to click or open something
Fix: None listed

What is CVE-2026-32309?

CVE-2026-32309 is a high-severity vulnerability in cryptomator, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official 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.

Weakness: CWE-319

Which versions are affected by CVE-2026-32309?

It affects 1 product.

Products include Cryptomator Cryptomator.

How do I fix CVE-2026-32309?

No fix has been published for CVE-2026-32309 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-32309 being exploited?

There is no known exploitation of CVE-2026-32309 in the wild and no public exploit code.

Sources

Also known as GHSA-vv33-h7qx-c264.