CVE-2026-33472Public exploitNetwork attack vector

OAuth token theft via port-based scheme confusion

Published Apr 16, 2026 · Updated Apr 16, 2026

Authentication bypass in Cryptomator 1.19.1 allows remote authenticated users to steal OAuth bearer tokens through a plaintext Hub exchange. CheckHostTrustController.getAuthority() substitutes schemes from port numbers, making HTTPS port 80 and HTTP authorities equal and bypassing consistency and HTTP-block checks. Exploitation requires write access to a cloud-synced vault.cryptomator file, victim interaction to unlock a Hub vault, and a position on the victim's network; the stolen token grants victim-level Hub API access but not vault data access.

CVSS severity4.8
Medium
EPSS probability0.11%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in Cryptomator 1.19.1 allows remote authenticated users to steal OAuth bearer tokens through a plaintext Hub exchange. CheckHostTrustController.getAuthority() substitutes schemes from port numbers, making HTTPS port 80 and HTTP authorities equal and bypassing consistency and HTTP-block checks. Exploitation requires write access to a cloud-synced vault.cryptomator file, victim interaction to unlock a Hub vault, and a position on the victim's network; the stolen token grants victim-level Hub API access but not vault data access.

The record

CVE
CVE-2026-33472
Published
Apr 16, 2026
Updated
Apr 16, 2026
Vendor
Cryptomator
Product
Cryptomator
Classifications
CWE-319, CWE-305, T1528, T1557
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 16, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 16, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.19.1, < 1.19.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Cryptomator · Cryptomatorversion=>= 1.19.1, < 1.19.2

Published CVSS scores

4.8GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-319Cleartext Transmission of Sensitive Information
CWE-305Authentication Bypass by Primary Weakness
T1528Steal Application Access Token
T1557Adversary-in-the-Middle

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo