CVE-2026-32310

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-32310", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-03-11T21:16:21.659Z", "datePublished": "2026-03-20T18:19:30.985Z", "dateUpdated": "2026-03-20T19:56:38.604Z"}, "containers": {"cna": {"title": "Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths", "problemTypes": [{"descriptions": [{"cweId": "CWE-22", "lang": "en", "description": "CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.1, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "CHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N", "version": "3.1"}}], "references": [{"name": "https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52"}, {"name": "https://github.com/cryptomator/cryptomator/pull/4180", "tags": ["x_refsource_MISC"], "url": "https://github.com/cryptomator/cryptomator/pull/4180"}, {"name": "https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40", "tags": ["x_refsource_MISC"], "url": "https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40"}, {"name": "https://github.com/cryptomator/cryptomator/releases/tag/1.19.1", "tags": ["x_refsource_MISC"], "url": "https://github.com/cryptomator/cryptomator/releases/tag/1.19.1"}], "affected": [{"vendor": "cryptomator", "product": "cryptomator", "versions": [{"version": ">= 1.6.0, <= 1.19.0", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-20T18:19:30.985Z"}, "descriptions": [{"lang": "en", "value": "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."}], "source": {"advisory": "GHSA-5phc-5pfx-hr52", "discovery": "UNKNOWN"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-03-20T19:56:28.979892Z", "id": "CVE-2026-32310", "options": [{"Exploitation": "poc"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-03-20T19:56:38.604Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-32310", "role": "CISA Coordinator", "options": [{"Exploitation": "poc"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-03-20T19:56:28.979892Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-03-20T19:56:34.253Z"}}], "cna": {"title": "Cryptomator: Unverified masterkeyfile key IDs can access arbitrary local or UNC paths", "source": {"advisory": "GHSA-5phc-5pfx-hr52", "discovery": "UNKNOWN"}, "metrics": [{"cvssV3_1": {"scope": "CHANGED", "version": "3.1", "baseScore": 4.1, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}}], "affected": [{"vendor": "cryptomator", "product": "cryptomator", "versions": [{"status": "affected", "version": ">= 1.6.0, <= 1.19.0"}]}], "references": [{"url": "https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52", "name": "https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://github.com/cryptomator/cryptomator/pull/4180", "name": "https://github.com/cryptomator/cryptomator/pull/4180", "tags": ["x_refsource_MISC"]}, {"url": "https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40", "name": "https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40", "tags": ["x_refsource_MISC"]}, {"url": "https://github.com/cryptomator/cryptomator/releases/tag/1.19.1", "name": "https://github.com/cryptomator/cryptomator/releases/tag/1.19.1", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "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."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-22", "description": "CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-20T18:19:30.985Z"}}}, "cveMetadata": {"cveId": "CVE-2026-32310", "state": "PUBLISHED", "dateUpdated": "2026-03-20T19:56:38.604Z", "dateReserved": "2026-03-11T21:16:21.659Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2026-03-20T18:19:30.985Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "cryptomator", "vendor": "cryptomator", "versions": [{"status": "affected", "version": ">= 1.6.0, <= 1.19.0"}]}], "source": "security-advisories@github.com"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:cryptomator:cryptomator:*:*:*:*:*:*:*:*", "matchCriteriaId": "F58B7CCD-1796-4352-BBD5-0872CFAF41B5", "versionEndIncluding": "1.19.0", "versionStartIncluding": "1.6.0", "vulnerable": true}], "negate": false, "operator": "OR"}, {"cpeMatch": [{"criteria": "cpe:2.3:o:microsoft:windows:*:*:*:*:*:*:*:*", "matchCriteriaId": "2CF61F35-5905-4BA9-AD7E-7DB261D2F256", "vulnerable": false}], "negate": false, "operator": "OR"}], "operator": "AND"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Cryptomator cifra datos almacenados en infraestructura en la nube. Desde la versi\u00f3n 1.6.0 hasta antes de la versi\u00f3n 1.19.1, la configuraci\u00f3n de la b\u00f3veda se analiza antes de que se verifique su integridad, y el cargador de masterkeyfile utiliza el keyId no verificado como una ruta del sistema de archivos. El cargador resuelve keyId.getSchemeSpecificPart() directamente contra la ruta de la b\u00f3veda e inmediatamente llama a Files.exists(...). Esto permite a una configuraci\u00f3n de b\u00f3veda maliciosa proporcionar escapes de directorio padre, rutas locales absolutas o rutas UNC (p. ej., masterkeyfile://atacante/share/masterkey.cryptomator). En Windows, la variante UNC es especialmente peligrosa porque Path.resolve(\"//atacante/share/...\") se convierte en \\\\atacante\\share\\..., por lo que la verificaci\u00f3n de existencia puede activar el acceso SMB saliente antes de que el usuario siquiera introduzca una frase de contrase\u00f1a. Este problema ha sido parcheado en la versi\u00f3n 1.19.1."}], "id": "CVE-2026-32310", "lastModified": "2026-06-17T10:35:32.470", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.1, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "CHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 2.3, "impactScore": 1.4, "source": "security-advisories@github.com", "type": "Secondary"}, {"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 1.4, "source": "nvd@nist.gov", "type": "Primary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-32310", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-03-20T19:56:28.979892Z", "version": "2.0.3"}}]}, "published": "2026-03-20T19:16:15.907", "references": [{"source": "security-advisories@github.com", "tags": ["Patch"], "url": "https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40"}, {"source": "security-advisories@github.com", "tags": ["Issue Tracking"], "url": "https://github.com/cryptomator/cryptomator/pull/4180"}, {"source": "security-advisories@github.com", "tags": ["Release Notes"], "url": "https://github.com/cryptomator/cryptomator/releases/tag/1.19.1"}, {"source": "security-advisories@github.com", "tags": ["Mitigation", "Vendor Advisory"], "url": "https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-22"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[1.6.0,1.19.0]"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "cryptomator", "source": "cna", "vendor": "cryptomator"}, "product": "cryptomator", "vendor": "cryptomator"}], "analysis": {"en": {"generated_at": "2026-03-25T23:53:44.571467+00:00", "value": {"mitigation_remediation": ["Upgrade Cryptomator to version 1.19.1 or later.", "Verify that all vault configuration files originate from trusted sources and remove or correct any that use arbitrary masterkeyfile paths."], "summary": {"action": "Patch", "impact": "Unauthorized file access including SMB shares"}, "threat_synthesis": {"affected_systems": "Cryptomator versions 1.6.0 through 1.19.0 on any platform detected by the CPE \u2013 particularly Windows, where UNC resolution is risky. The vulnerability does not affect earlier versions or 1.19.1 and later. The affected software is the Cryptomator desktop application distributed by the vendor cryptomator:cryptomator. Windows operating systems are especially relevant because of the SMB path resolution.", "description_and_impact": "Cryptomator encrypts cloud data through vaults, but from version 1.6.0 to just before 1.19.1 the system parses the vault configuration before checking its integrity. The masterkeyfile loader treats the keyId supplied in the configuration as a file\u2011system path without validation. An attacker can insert parent\u2011directory escapes or absolute paths \u2013 for example using a masterkeyfile://prefix that resolves to a UNC share \u2013 so the application will call the path existence check before any password is entered. This can allow reading of arbitrary local files or triggering outbound SMB requests to attacker controlled shares, potentially exposing sensitive data.", "risk_and_exploitability": "The CVSS score of 4.1 reflects moderate risk; the EPSS score shows less than 1% probability of exploitation today, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation requires a user to load or open a vault whose configuration contains a malicious masterkeyfile keyId, which the attacker can supply via a compromised cloud folder or a phishing attachment. Once the vault is opened, the existence check for the supplied path occurs before the user enters the vault password, so the exploit can succeed without further interaction. Consequently, the main risk is local or network file disclosure rather than remote code execution."}}}}, "created": "2026-03-23T09:53:03.246584+00:00", "updated": "2026-03-26T12:20:37.312261+00:00", "vendors": ["cryptomator", "cryptomator$PRODUCT$cryptomator"]}