VulnerabilityPublished 20 Mar 2026

CVE-2026-32317: cryptomator android · Origin Validation Error

Affects cryptomator androidSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 1.12.3 soon.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 3.1 base score

7.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.06% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.12.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade android and cryptomator/android to 1.12.3.

Affected software

Product	Affected	Fixed in
cryptomatorandroid	Affected <1.12.3	Fixed in 1.12.3
GitHubcryptomator/android`pkg:github/cryptomator/android`Other threats	Affected <1.12.3	Fixed in 1.12.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations and users should immediately update Cryptomator for Android to version 1.12.3 or later, where the issue is patched. Beyond patching, it is critical to enforce strict access controls on vault.cryptomator files to prevent unauthorized modification, including using secure storage solutions and applying file integrity monitoring. Network segmentation and endpoint security measures should be implemented to reduce the risk of attackers gaining the ability to alter vault files. Additionally, educating users about the risks of unlocking vaults in untrusted environments can reduce exposure. Organizations should also consider implementing multi-factor authentication (MFA) for cloud services integrated with Cryptomator to limit the impact of token theft. Regular audits of vault configuration files and monitoring for unusual authentication activity can help detect exploitation attempts early. Finally, developers should review and enhance origin validation and endpoint authentication mechanisms in client applications to prevent similar vulnerabilities.

Description

CVE-2026-32317 is a high-severity vulnerability in Cryptomator for Android versions prior to 1.12.3. It stems from an origin validation error where the client trusted endpoints specified in the vault configuration file without verifying host authenticity. This flaw allows an attacker who can tamper with the vault.cryptomator file to mix legitimate authentication endpoints with malicious API endpoints, leading to token exfiltration via a man-in-the-middle attack during the Hub key loading process. Exploitation requires the attacker to have the capability to alter the vault configuration file and the user to unlock a Hub-backed vault with a vulnerable client version. The vulnerability impacts confidentiality by exposing authentication tokens but does not affect availability. The issue has been patched in version 1.12.

Impact

This vulnerability primarily threatens the confidentiality of user authentication tokens, which can be exfiltrated by attackers capable of modifying the vault configuration file. Such token theft could allow unauthorized access to encrypted vaults or associated cloud services, potentially exposing sensitive user data. The integrity of the vault configuration is also compromised, as attackers can inject malicious endpoints, undermining trust in the client’s communication channels. Although availability is not directly impacted, the breach of confidentiality could lead to broader security incidents, including unauthorized data access or lateral movement within organizational environments. Organizations relying on Cryptomator Android clients for secure cloud file encryption, especially in environments where vault files are stored on shared or less secure storage, face increased risk. Attackers with network or local access to alter vault files could exploit this vulnerability to intercept authentication tokens, facilitating further attacks or data breaches. The vulnerability’s exploitation complexity is moderate, requiring user interaction and the ability to tamper with vault files, but the impact on confidentiality is high, making it a significant risk for users and organizations prioritizing data privacy and security.

CWE-346Origin Validation Error (opens in a new tab)
Class weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not properly verify that the source of data or communication is valid.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V14.5.2 (opens in a new tab)
V14.5.3 (opens in a new tab)
V1.4.4 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cache Poisoning (opens in a new tab)
DNS Cache Poisoning (opens in a new tab)
Exploit Script-Based APIs (opens in a new tab)
Application API Message Manipulation via Man-in-the-Middle (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-354Improper Validation of Integrity Check Value (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product does not validate or incorrectly validates the integrity check values or "checksums" of a message.
Implementation
The protocol specification describes the algorithm used for calculating the checksum. It is then a matter of implementing the calculation and verifying that the calculated checksum and the received checksum match.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
Attack patterns
Checksum Spoofing (opens in a new tab)
Padding Oracle Crypto Attack (opens in a new tab)
Manipulating Writeable Configuration Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-451User Interface (UI) Misrepresentation of Critical Information (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks.
Implementation · Input Validation
Perform data validation (e.g. syntax, length, etc.) before interpreting the data.
Architecture and Design · Output Encoding
Create a strategy for presenting information, and plan for how to display unusual characters.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Spear Phishing (opens in a new tab)
Mobile Phishing (opens in a new tab)
Phishing (opens in a new tab)
Resource Location Spoofing (opens in a new tab)
Action Spoofing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-923Improper Restriction of Communication Channel to Intended Endpoints (opens in a new tab)
Class weakness
The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
Attack patterns
Contradictory Destinations in Traffic Routing Schemes (opens in a new tab)
Android Activity Hijack (opens in a new tab)
DHCP Spoofing (opens in a new tab)
Infrastructure Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 19:37 UTC

WeaknessesCWE-346, CWE-354, CWE-451 +1

Technical details

References

Community reviews

Related threats