Cryptomator for iOS provides client-side encryption for cloud-stored files, ensuring data confidentiality across platforms. Prior to version 2.8.3, a critical vulnerability (CVE-2026-32318) existed due to improper origin validation (CWE-346) in the vault configuration file handling. Specifically, the client trusted endpoints listed in the vault.cryptomator file without performing adequate host authenticity checks. This flaw allowed an attacker with the ability to modify the vault configuration file to inject malicious API endpoints alongside legitimate authentication endpoints. During the Hub key loading mechanism, this mixing of endpoints could facilitate a man-in-the-middle (MitM) attack, enabling token exfiltration and partial compromise of the authentication process. The vulnerability also relates to weaknesses in access control (CWE-354), improper authorization (CWE-451), and improper verification of cryptographic signatures or hashes (CWE-923). Exploitation requires the attacker to have write access to the vault.cryptomator file and the victim to unlock a Hub-backed vault using an affected client version. The vulnerability has been assigned a CVSS v3.1 score of 7.6 (high severity), reflecting its network attack vector, low attack complexity, requirement for privileges and user interaction, and significant confidentiality impact. The issue was patched in Cryptomator iOS version 2.8.3, which introduced proper host authenticity checks to prevent endpoint tampering.

The vulnerability poses a significant risk to users of Cryptomator iOS clients prior to version 2.8.3, particularly those using Hub-backed vaults in environments where an attacker can modify the vault configuration file. Successful exploitation can lead to token exfiltration, undermining the confidentiality of encrypted data and potentially enabling unauthorized access to user vaults. This compromises the integrity of the authentication process and may facilitate further attacks on cloud-stored data. Organizations relying on Cryptomator for secure cloud file encryption could face data breaches, loss of trust, and compliance violations if attackers exploit this flaw. Since the attack requires modification of the vault file, environments with shared or compromised devices, or where attackers have local or network-level access to storage, are at higher risk. Although no known exploits are reported in the wild, the vulnerability's characteristics make it a credible threat in targeted attack scenarios.

Organizations and users should immediately upgrade Cryptomator for iOS to version 2.8.3 or later to apply the official patch that enforces strict host authenticity validation for vault configuration endpoints. Additionally, users should ensure the integrity of their vault files by restricting write permissions to trusted users and devices only. Employing device-level security controls such as full disk encryption, secure boot, and endpoint protection can reduce the risk of unauthorized modification of vault files. Network segmentation and monitoring can help detect suspicious activities indicative of man-in-the-middle attacks. For environments with high security requirements, consider implementing additional integrity verification mechanisms for vault configuration files, such as cryptographic signatures or checksums verified out-of-band. Regularly auditing and reviewing access controls on cloud storage and local devices will further mitigate risks. Finally, educating users about the importance of applying updates promptly and recognizing suspicious behaviors during vault unlocking can enhance overall security posture.