dbcve.org
CryptomatorApplication

CVE-2026-32317

MEDIUM · 5.9 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to after 1.12.2 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable 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 for Android offers multi-platform transparent client-side encryption for files in the cloud. Prior to version 1.12.3, an integrity check vulnerability allows an attacker 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.12.3.

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 for Android versions before 1.12.3 lack proper host authenticity validation when processing vault configuration files (vault.cryptomator). The client trusts endpoints specified in the vault config without verifying the host's identity, enabling a man-in-the-middle attacker to mix a legitimate auth endpoint with a malicious API endpoint to exfiltrate authentication tokens.

MitigationUpdate Cryptomator for Android to version 1.12.3 or later to obtain the patch. Users of Hub-backed vaults should verify their client versions immediately.

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

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/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 Cryptomator for Android version
    Open the device Settings > Apps > Cryptomator > App info, or open the Google Play Store app page for Cryptomator and view the version number under the app name
    Affected if The displayed version is 1.12.2 or any earlier version number
  2. Confirm vault config file usage
    This vulnerability affects any use of vault.cryptomator configuration files - the flaw is present in the version itself when processing these files
    Affected if Any vault configuration file is opened using an affected version of the app

If the installed Cryptomator for Android version is 1.12.2 or earlier, the environment is affected by this host authenticity validation vulnerability in vault config processing.

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 a release after 1.12.2
Interim mitigation

Update Cryptomator for Android to version 1.12.3 or later to obtain the patch. Users of Hub-backed vaults should verify their client versions immediately.

Recommended fix High confidence

Cryptomator for Android version 1.12.3

  1. 1. Check the current installed version of Cryptomator on the Android device.
  2. 2. Navigate to the Google Play Store or appropriate app store for Cryptomator.
  3. 3. Search for Cryptomator and verify if version 1.12.3 or later is available.
  4. 4. If an update is available, download and install the latest version (1.12.3 or later).
  5. 5. After updating, verify the new version by checking the app's About or Settings section.
  6. 6. Test unlocking a Hub-backed vault to confirm the integrity check vulnerability is resolved.

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

Fix this in Cryptomator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32317 — 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-32317 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