CVE-2026-32303

Cryptomator: 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 encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, an integrity check vulnerability allows an attacker to 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.19.1.

Analysis

AI-generated

Technical impact

Cryptomator normally encrypts files stored on cloud services and relies on an integrity check of the vault configuration file. An attacker who can modify this file bypasses host authenticity validation during Hub key loading, creating a man‑in‑the‑middle scenario. The vulnerability enables a malicious endpoint to be paired with a legitimate authentication endpoint, allowing the extraction of access tokens used to communicate with the cloud. The flaw is characterized by CWE‑346, CWE‑354, CWE‑451, and CWE‑923, and has a CVSS score of 7.6, indicating high severity.

Affected Systems

Cryptomator, the open‑source client for encrypted cloud storage, is affected. Users who run versions prior to 1.19.1 and unlock Hub‑backed vaults in environments where an attacker can alter the vault.cryptomator file are vulnerable. Version 1.19.1 contains a patch that restores integrity verification of the configuration file and the existing hosts list. The vulnerability applies to all releases before that point.

Risk and Exploitability

The risk is high due to the potential for token theft, but the EPSS score <1% indicates low likelihood of widespread exploitation at present. The vulnerability is not cataloged in CISA’s KEV list. Exploitation requires the attacker to have the ability to tamper with the configuration file on the client machine or the network path used to retrieve it, making it most likely in scenarios where local credentials are compromised or the user accepts malicious updates. The attack path is relatively straightforward once file tampering is possible, and it can result in unauthorized API calls to the cloud provider on the victim’s behalf.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Install Cryptomator version 1.19.1 or later to apply the integrity‑check fix.
  • Verify that the vault.cryptomator file is signed or use file integrity monitoring tools.
  • Restrict file permissions so only the owner can modify the vault configuration.
  • Audit and monitor for unexpected changes to vault.cryptomator files.

Generated by OpenCVE AI on March 26, 2026 at 16:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Cryptomator
Cryptomator cryptomator
Vendors & Products Cryptomator
Cryptomator cryptomator
Type Values Removed Values Added
Description Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, an integrity check vulnerability allows an attacker to 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.19.1.
Title Cryptomator: 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 23, 2026, 9:41 PM
Reserved
Mar 11, 2026, 9:16 PM
Status
Analyzed
Published
Mar 20, 2026, 6:16 PM
Modified
Jun 17, 2026, 10:35 AM