What’s Vulnerable › Vulnerabilities
CVE-2026-33472: Cryptomator Hub OAuth token exchange HTTP downgrade via getAuthority() scheme confusion (CVE-2026-32303 bypass)
- Severity: medium (CVSS 4.8 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.1% probability of exploitation in the next 30 days
- Public exploit or detection template: yes
- Published: 2026-04-16 · updated 2026-06-17
- Weakness: CWE-305
Description
Cryptomator is an open-source client-side encryption application for cloud storage. Version 1.19.1 contains a logic flaw in CheckHostTrustController.getAuthority() that allows an attacker to bypass the security fix for CVE-2026-32303. The method hardcodes the URI scheme based on port number, causing HTTPS URLs with port 80 to produce the same authority string as HTTP URLs, which defeats both the consistency check and the HTTP block validation. An attacker with write access to a cloud-synced vault.cryptomator file can craft a Hub configuration where apiBaseUrl and authEndpoint use HTTPS with port 80 to pass auto-trust validation, while tokenEndpoint uses plaintext HTTP. The vault is auto-trusted without user prompt, and a network-positioned attacker can intercept the OAuth token exchange to access the Cryptomator Hub API as the victim. This issue has been fixed in version 1.19.2.
Affected products
- cryptomator: before 1.19.2 — fixed in 1.19.2
How to fix
Upgrade to a fixed version: cryptomator 1.19.2. Check the vendor advisory for mitigations.
References
- https://github.com/cryptomator/cryptomator/pull/4179
- https://github.com/cryptomator/cryptomator/releases/tag/1.19.2
- https://github.com/cryptomator/cryptomator/security/advisories/GHSA-9q8x-whrw-x44p
- https://github.com/cryptomator/cryptomator/security/advisories/GHSA-9q8x-whrw-x44p
Get alerted when CVE-2026-33472 or the next vulnerability affects your stack