{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32309 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32309 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32309 is a high-severity vulnerability in cryptomator, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-32309 and fix it if it is affected.\n\nWhat it is: CVE-2026-32309 is a high-severity vulnerability in cryptomator, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-32309 in the wild and no public exploit code.\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-32309/ (Markdown: https://insights.sbomify.com/CVE-2026-32309/index.md)","id":"CVE-2026-32309","markdown":"https://insights.sbomify.com/CVE-2026-32309/index.md","name":"CVE-2026-32309","record":{"aliases":["GHSA-vv33-h7qx-c264"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Cryptomator desktop client","requires_auth":"none","summary":"An active network attacker can intercept or tamper with Cryptomator Hub authentication traffic due to lack of HTTPS enforcement, exposing bearer tokens.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cryptomator","vendor":"cryptomator"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, the Hub-based unlock flow explicitly supports hub+http and consumes Hub endpoints from vault metadata without enforcing HTTPS. As a result, a vault configuration can drive OAuth and key-loading traffic over plaintext HTTP or other insecure endpoint combinations. An active network attacker can tamper with or observe this traffic. Even when the vault key is encrypted for the device, bearer tokens and endpoint-level trust decisions are still exposed to downgrade and interception. This issue has been patched in version 1.19.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes","id":"CVE-2026-32309","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths","id":"CVE-2026-32310"},"packages":[],"prev":{"headline":"OneUptime: Stored XSS via Mermaid Diagram Rendering (securityLevel: \"loose\")","id":"CVE-2026-32308"},"products":["cryptomator"],"published":"2026-03-20","related":[{"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-27","vendors":["cryptomator"]},"summary":"An active network attacker can intercept or tamper with Cryptomator Hub authentication traffic due to lack of HTTPS enforcement, exposing bearer tokens.","url":"https://insights.sbomify.com/CVE-2026-32309/"}