CVE-2026-32310

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

March 20, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Unverified masterkeyfile key IDs can access arbitrary local or UNC paths · Advisory · cryptomator/cryptomator · GitHub

https://github.com/cryptomator/cryptomator/security/advisories/GHSA-5phc-5pfx-hr52
github_release Patch Available

1.19.1

Patch available: cryptomator/cryptomator 1.19.1

https://github.com/cryptomator/cryptomator/releases/tag/1.19.1
github_pr

don't load masterkey from arbitrary paths

Fix merged in cryptomator/cryptomator PR #4180 on 2026-03-12 — awaiting tagged release

https://github.com/cryptomator/cryptomator/pull/4180
github_commit

commit 1e3dfe3de162 (cryptomator/cryptomator)

Fix landed in cryptomator/cryptomator commit 1e3dfe3de162 — awaiting tagged release

https://github.com/cryptomator/cryptomator/commit/1e3dfe3de1623b1b85d24db91e49d31d1ea11f40

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 16:38 UTCOSV refresh
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 37 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 11:00 UTCEG score recompute
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 07:10 UTCEG score recompute
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 21:51 UTCEG score recompute
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 04:24 UTCEG score recompute
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 05:16 UTCEG score recompute
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 06:44 UTCEG score recompute
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 17:14 UTCEG score recompute
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-06 01:27 UTCEG score recompute
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 15:10 UTCEPSS rescore
  28. 2026-08-04 10:38 UTCEPSS rescore
  29. 2026-08-04 00:35 UTCEG score recompute
  30. 2026-08-03 10:36 UTCEPSS rescore
  31. 2026-08-02 16:10 UTCEG score recompute
  32. 2026-08-02 02:27 UTCEPSS rescore
  33. 2026-08-01 04:16 UTCEPSS rescore
  34. 2026-07-30 16:28 UTCEPSS rescore
  35. 2026-07-30 01:30 UTCEPSS rescore
  36. 2026-07-27 14:35 UTCEG score recompute
  37. 2026-07-27 14:27 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-32310?
CVE-2026-32310 is a medium vulnerability published on March 20, 2026. 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()…
When was CVE-2026-32310 disclosed?
CVE-2026-32310 was first published in the National Vulnerability Database on March 20, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32310 actively exploited?
CVE-2026-32310 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.5% of all scored CVEs.
What is the CVSS score of CVE-2026-32310?
CVE-2026-32310 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-32310?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32310, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-32310

Explore →

Is Your Infrastructure Affected by CVE-2026-32310?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs