{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32310 exists.","fix":"No fix has been published for CVE-2026-32310 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32310 is a medium-severity path traversal 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-32310 and fix it if it is affected.\n\nWhat it is: CVE-2026-32310 is a medium-severity path traversal 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32310 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-32310/ (Markdown: https://insights.sbomify.com/CVE-2026-32310/index.md)","id":"CVE-2026-32310","markdown":"https://insights.sbomify.com/CVE-2026-32310/index.md","name":"CVE-2026-32310","record":{"aliases":["GHSA-5phc-5pfx-hr52"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Cryptomator encryption tool","requires_auth":"low_privilege","summary":"A malicious vault configuration can force Cryptomator to access arbitrary local or network paths, potentially leaking data or triggering SMB requests before authentication.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cryptomator","vendor":"cryptomator"}],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Cryptomator encrypts data being stored on cloud infrastructure. From version 1.6.0 to before version 1.19.1, vault configuration is parsed before its integrity is verified, and the masterkeyfile loader uses the unverified keyId as a filesystem path. The loader resolves keyId.getSchemeSpecificPart() directly against the vault path and immediately calls Files.exists(...). This allows a malicious vault config to supply parent-directory escapes, absolute local paths, or UNC paths (e.g., masterkeyfile://attacker/share/masterkey.cryptomator). On Windows, the UNC variant is especially dangerous because Path.resolve(\"//attacker/share/...\") becomes \\\\attacker\\share\\..., so the existence check can trigger outbound SMB access before the user even enters a passphrase. 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":"weaponised"},"has_fix":false,"headline":"Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths","id":"CVE-2026-32310","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Command Injection and Docker container escape allows root on host machine","id":"CVE-2026-32311"},"packages":[],"prev":{"headline":"Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes","id":"CVE-2026-32309"},"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: 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-03-20","vendors":["cryptomator"]},"summary":"A malicious vault configuration can force Cryptomator to access arbitrary local or network paths, potentially leaking data or triggering SMB requests before authentication.","url":"https://insights.sbomify.com/CVE-2026-32310/"}