{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33472 exists.","fix":"No fix has been published for CVE-2026-33472 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-33472 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33472 exists.\n\nAffected product: cryptomator. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33472/ (Markdown: https://insights.sbomify.com/CVE-2026-33472/index.md)","id":"CVE-2026-33472","markdown":"https://insights.sbomify.com/CVE-2026-33472/index.md","name":"CVE-2026-33472","record":{"aliases":["GHSA-9q8x-whrw-x44p"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cryptomator client","requires_auth":"low_privilege","summary":"Attackers can bypass HTTPS enforcement in Cryptomator Hub OAuth flows, allowing interception of tokens and unauthorized API access via network position.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cryptomator","vendor":"cryptomator"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-305","name":"Authentication Bypass by Primary Weakness"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cryptomator Hub OAuth token exchange HTTP downgrade via getAuthority() scheme confusion (CVE-2026-32303 bypass)","id":"CVE-2026-33472","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Vikunja has TOTP Reuse During Validity Window","id":"CVE-2026-33473"},"packages":[],"prev":{"headline":"nimiq-block has skip block quorum bypass via out-of-range BitSet indices \u0026 u16 truncation","id":"CVE-2026-33471"},"products":["cryptomator"],"published":"2026-04-16","related":[{"cvss_score":8.7,"headline":"Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes","id":"CVE-2026-32309","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2022-25366","kev_date_added":null,"published":"2022-02-19"},{"cvss_score":7.6,"headline":"Cryptomator: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32303","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.6,"headline":"Cryptomator for Android: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32317","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.6,"headline":"Cryptomator for IOS: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32318","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7,"headline":"Cryptomator's MSI installer allows local privilege escalation","id":"CVE-2023-37907","kev_date_added":null,"published":"2023-07-25"},{"cvss_score":5.5,"headline":"Cryptomator vulnerable to Local Elevation of Privileges","id":"CVE-2023-39520","kev_date_added":null,"published":"2023-08-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-20","vendors":["cryptomator"]},"summary":"Attackers can bypass HTTPS enforcement in Cryptomator Hub OAuth flows, allowing interception of tokens and unauthorized API access via network position.","url":"https://insights.sbomify.com/CVE-2026-33472/"}