CVE-2026-32317

Cryptomator for Android: Tampered vault configuration allows MITM attack on Hub API

Published Mar 20, 2026 CVSS 3.1 · 7.6 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability resides in the integrity verification of the vault.cryptomator file used by Cryptomator for Android. In versions before 1.12.3 the application accepts the endpoint URLs listed in that file without performing host authenticity checks. An attacker who can alter the file can replace a legitimate Hub API URL with a malicious endpoint. When the client authenticates to the tampered endpoint it transmits the user’s access token, allowing the attacker to exfiltrate the token and later gain unauthorized access to the user’s cloud data.

Affected Systems

All Android installations of Cryptomator older than 1.12.3 that are configured to use Hub for vaults are affected. Both the Android OS platform and any cloud provider accessed through the Hub API are impacted as long as the client trusts the modified configuration. The problem is confined to devices running the unpatched client.

Risk and Exploitability

The CVSS score of 7.6 classifies the flaw as high severity. The EPSS score is below 1 %, and it is not listed as a known exploited vulnerability. Based on the description, it is inferred that the attacker must have the ability to modify the vault.cryptomator file; this requirement implies that local access, a privilege‑elevating vulnerability, or another mechanism that grants write permissions would be needed. Once the file is altered, the attacker can perform a man‑in‑the‑middle attack and harvest authentication tokens. The lack of host verification allows the client to communicate with any URL specified in the file, making the vulnerability straightforward once the configuration is compromised.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Cryptomator Android to version 1.12.3 or later
  • Verify that the vault.cryptomator file has not been tampered with and that endpoints correspond to the legitimate service
  • Monitor Cryptomator release notes for additional guidance

Generated by OpenCVE AI on March 26, 2026 at 17:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Cryptomator cryptomator
Google
Google android
CPEs cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*
cpe:2.3:o:google:android:*:*:*:*:*:*:*:*
Vendors & Products Cryptomator cryptomator
Google
Google android
Type Values Removed Values Added
First Time appeared Cryptomator
Cryptomator android
Vendors & Products Cryptomator
Cryptomator android
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Cryptomator for Android: Tampered vault configuration allows MITM attack on Hub API
Weaknesses CWE-346
CWE-354
CWE-451
CWE-923
References
Metrics cvssV3_1

{'score': 7.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N'}

Weaknesses
  • CWE-346

    Origin Validation Error

  • CWE-354

    Improper Validation of Integrity Check Value

  • CWE-451

    User Interface (UI) Misrepresentation of Critical Information

  • CWE-923

    Improper Restriction of Communication Channel to Intended Endpoints

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 20, 2026, 6:55 PM
Reserved
Mar 11, 2026, 9:16 PM
Status
Analyzed
Published
Mar 20, 2026, 7:16 PM
Modified
Jun 17, 2026, 10:35 AM