dbcve.org
CryptomatorApplication

CVE-2026-32309

HIGH · 7.5 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 1.19.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cryptomator versions prior to 1.19.1 have a Hub-based unlock flow that supports hub+http and consumes Hub endpoints from vault metadata without enforcing HTTPS. This allows vault configurations to direct OAuth and key-loading traffic over plaintext HTTP, exposing bearer tokens and authentication traffic to active network attackers who can intercept or modify the unprotected communications.

MitigationUpgrade Cryptomator to version 1.19.1 or later, which patches the vulnerability by enforcing HTTPS for Hub endpoints. Verify that existing vault configurations using Hub unlock function correctly after the upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CryptomatorApplication
Affected:< 1.19.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Cryptomator version
    Locate and inspect the installed Cryptomator application version through your system package manager, application settings, or about dialog. Compare this version number against the affected range of versions prior to 1.19.1.
    Affected if The installed version is lower than 1.19.1
  2. Identify if Hub unlock is in use
    Examine your vault configurations or unlock workflows to determine whether the Hub-based unlock flow (hub+http or hub+https scheme) is being used to access vaults.
    Affected if Vaults are configured to use Hub unlock with the hub+http scheme
  3. Inspect vault configuration files for HTTP Hub endpoints
    Locate and review vault configuration files or metadata where Hub endpoints are specified. Look for any Hub URL entries using the http:// scheme rather than https://.
    Affected if Vault configurations contain Hub endpoint URLs beginning with http:// instead of https://

You are affected if Cryptomator version is below 1.19.1 AND you use Hub unlock with vault configurations pointing to HTTP-based Hub endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.19.1 or later
Fixed in 1.19.1
Interim mitigation

Upgrade Cryptomator to version 1.19.1 or later, which patches the vulnerability by enforcing HTTPS for Hub endpoints. Verify that existing vault configurations using Hub unlock function correctly after the upgrade.

Recommended fix High confidence

1.19.1

  1. 1. Check current Cryptomator version by opening the application and navigating to Help > About or checking the installed programs list
  2. 2. Download Cryptomator version 1.19.1 or later from the official GitHub releases page (github.com/cryptomator/cryptomator/releases) or the official website
  3. 3. Install the downloaded version, replacing the existing installation
  4. 4. Verify the upgrade was successful by checking the version number again in the application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cryptomator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32309 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32309 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data