# CVE-2026-33472: Cryptomator Hub OAuth token exchange HTTP downgrade via getAuthority() scheme confusion (CVE-2026-32303 bypass)

> Attackers can bypass HTTPS enforcement in Cryptomator Hub OAuth flows, allowing interception of tokens and unauthorized API access via network position.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-9q8x-whrw-x44p

## What is CVE-2026-33472?

CVE-2026-33472 is a medium-severity vulnerability in cryptomator, published on 16 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2026-33472?

It affects 1 product.


Products: Cryptomator Cryptomator.

## How do I fix CVE-2026-33472?

No fix has been published for CVE-2026-33472 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33472 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33472 exists.

## Other vulnerabilities in cryptomator

- [CVE-2026-32309](https://insights.sbomify.com/CVE-2026-32309/): Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes (high 8.7)
- [CVE-2022-25366](https://insights.sbomify.com/CVE-2022-25366/): Code injection in n/a (high 7.8)
- [CVE-2026-32303](https://insights.sbomify.com/CVE-2026-32303/): Cryptomator: Tampered vault configuration allows MITM attack on Hub API (high 7.6)
- [CVE-2026-32317](https://insights.sbomify.com/CVE-2026-32317/): Cryptomator for Android: Tampered vault configuration allows MITM attack on Hub API (high 7.6)
- [CVE-2026-32318](https://insights.sbomify.com/CVE-2026-32318/): Cryptomator for IOS: Tampered vault configuration allows MITM attack on Hub API (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33472 and fix it if it is affected.

What it is: CVE-2026-33472 is a medium-severity vulnerability in cryptomator, published on 16 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33472 exists.

Affected product: cryptomator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33472/ (Markdown: https://insights.sbomify.com/CVE-2026-33472/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33472
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33472
- OSV: https://osv.dev/vulnerability/CVE-2026-33472

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33472/
Summaries are generated and may contain mistakes; the official description above is the record.