CVE-2026-32303: Cryptomator Auth Bypass Vulnerability

CVE-2026-32303 Overview

CVE-2026-32303 is an integrity check vulnerability in Cryptomator, a popular client-side encryption application for cloud storage. The flaw affects the Hub key loading mechanism, allowing attackers who can modify the vault.cryptomator configuration file to perform man-in-the-middle (MITM) attacks. Prior to version 1.19.1, the Cryptomator client trusted endpoints specified in the vault configuration without performing proper host authenticity verification, enabling potential token exfiltration through endpoint manipulation.

Critical Impact

Attackers can tamper with vault configuration files to redirect authentication tokens to malicious endpoints, potentially compromising encrypted vault access for Hub-backed vaults.

Affected Products

• Cryptomator versions prior to 1.19.1
• Hub-backed vault configurations
• Environments where attackers can modify vault.cryptomator files

Discovery Timeline

• 2026-03-20 - CVE-2026-32303 published to NVD
• 2026-03-26 - Last updated in NVD database

Technical Details for CVE-2026-32303

Vulnerability Analysis

This vulnerability stems from insufficient validation of endpoint configurations within the Cryptomator client when loading Hub-backed vaults. The application reads authentication and API endpoint URLs from the vault.cryptomator configuration file but fails to verify that these endpoints belong to the same trusted host. This Origin Validation Error (CWE-346) allows an attacker to craft a malicious vault configuration that combines a legitimate authentication endpoint with an attacker-controlled API endpoint.

When a user unlocks a Hub-backed vault, the client performs authentication against the configured auth endpoint and receives authentication tokens. These tokens are then used for subsequent API calls. By manipulating the vault configuration, an attacker can direct the client to exfiltrate these authentication tokens to a malicious server while maintaining the appearance of legitimate authentication flow.

Root Cause

The root cause is the lack of host authenticity checks when processing endpoint configurations from the vault.cryptomator file. The client implicitly trusted all configured endpoints without verifying that the authentication endpoint and API endpoint shared the same origin or belonged to a trusted host list. This design flaw allowed mixed endpoint configurations that could redirect sensitive authentication tokens to unauthorized destinations.

Attack Vector

The attack requires network-level access and the ability to modify the vault.cryptomator configuration file stored alongside the encrypted vault. Attack scenarios include:

1. An attacker with access to the cloud storage where the vault resides modifies the vault.cryptomator file
2. The attacker configures a legitimate authentication endpoint paired with a malicious API endpoint under their control
3. When a victim unlocks the vault, authentication proceeds normally against the legitimate auth server
4. The resulting authentication tokens are then sent to the attacker's malicious API endpoint
5. The attacker captures these tokens and can potentially use them to access the victim's vault

The vulnerability specifically impacts users of Hub-backed vaults in scenarios where the attacker can alter vault configuration files, such as through compromised cloud storage accounts or shared storage environments.

Detection Methods for CVE-2026-32303

Indicators of Compromise

• Unexpected modifications to vault.cryptomator configuration files
• Vault configuration files containing mismatched authentication and API endpoint domains
• Network connections from Cryptomator to unusual or unauthorized external hosts
• Authentication token submissions to non-Cryptomator Hub domains

Detection Strategies

• Monitor file integrity of vault.cryptomator files using file integrity monitoring (FIM) solutions
• Implement network traffic analysis to detect Cryptomator clients connecting to unauthorized endpoints
• Review cloud storage access logs for unauthorized modifications to vault configuration files
• Configure endpoint detection to alert on Cryptomator processes making connections to unknown hosts

Monitoring Recommendations

• Enable detailed logging for cloud storage account access and file modifications
• Deploy network monitoring rules to baseline normal Cryptomator Hub communication patterns
• Implement alerts for vault configuration file changes in shared or cloud-synchronized storage
• Regularly audit vault configurations in enterprise deployments for endpoint consistency

How to Mitigate CVE-2026-32303

Immediate Actions Required

• Upgrade Cryptomator to version 1.19.1 or later immediately
• Review existing vault.cryptomator configuration files for signs of tampering
• Verify that authentication and API endpoints in vault configurations point to legitimate Cryptomator Hub servers
• Consider temporarily restricting access to vault configuration files pending upgrade

Patch Information

Cryptomator has addressed this vulnerability in version 1.19.1. The fix implements proper host authenticity checks for endpoints loaded from vault configurations, preventing mixed endpoint attacks. Users should upgrade to this version or later to remediate the vulnerability.

For detailed technical information, refer to the GitHub Security Advisory GHSA-34rf-rwr3-7g43. The specific code changes can be reviewed in GitHub Pull Request #4179 and the associated commit.

Workarounds

• Restrict write access to directories containing vault.cryptomator configuration files
• Use local-only vaults instead of Hub-backed vaults until the patch is applied
• Implement strict access controls on cloud storage accounts hosting encrypted vaults
• Monitor and validate vault configuration files before unlocking vaults in untrusted environments

# Verify Cryptomator version after upgrade
cryptomator --version
# Expected: 1.19.1 or higher

# Check vault configuration file integrity (example hash comparison)
sha256sum /path/to/vault/vault.cryptomator