{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32303 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32303 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32303 is a high-severity vulnerability in cryptomator, published on 20 Mar 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-32303 and fix it if it is affected.\n\nWhat it is: CVE-2026-32303 is a high-severity vulnerability in cryptomator, published on 20 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-32303 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-32303/ (Markdown: https://insights.sbomify.com/CVE-2026-32303/index.md)","id":"CVE-2026-32303","markdown":"https://insights.sbomify.com/CVE-2026-32303/index.md","name":"CVE-2026-32303","record":{"aliases":["GHSA-34rf-rwr3-7g43"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Cryptomator client","requires_auth":"low_privilege","summary":"Attackers can tamper with vault configuration to bypass host authenticity checks, enabling man-in-the-middle attacks and token exfiltration.","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":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"},{"id":"CWE-451","name":"User Interface (UI) Misrepresentation of Critical Information"},{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"},{"id":"CWE-346","name":"Origin Validation Error"}],"description":"Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, an integrity check vulnerability allows an attacker to tamper with the vault configuration file leading to a man-in-the-middle vulnerability in Hub key loading mechanism. Before this fix, the client trusted endpoints from the vault config without host authenticity checks, which could allow token exfiltration by mixing a legitimate auth endpoint with a malicious API endpoint. Impacted are users unlocking Hub-backed vaults with affected client versions in environments where an attacker can alter the vault.cryptomator file. 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: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Locutus: RCE via unsanitized input in create_function()","id":"CVE-2026-32304"},"packages":[],"prev":{"headline":"OpenClaw: Untrusted web origins can obtain authenticated operator.admin access in trusted-proxy mode","id":"CVE-2026-32302"},"products":["cryptomator"],"published":"2026-03-20","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 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":"partial"},"state":"PUBLISHED","updated":"2026-03-23","vendors":["cryptomator"]},"summary":"Attackers can tamper with vault configuration to bypass host authenticity checks, enabling man-in-the-middle attacks and token exfiltration.","url":"https://insights.sbomify.com/CVE-2026-32303/"}