CVE-2026-32303

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% 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.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: 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. 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.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
31(Track)
EG Risk 31/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
Severity59% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

March 20, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 6, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available

Tampered vault configuration allows MITM attack on Hub API · Advisory · cryptomator/cryptomator · GitHub

https://github.com/cryptomator/cryptomator/security/advisories/GHSA-34rf-rwr3-7g43
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

Hub: Trust on first use

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

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

commit 6b82abcd8044 (cryptomator/cryptomator)

Fix landed in cryptomator/cryptomator commit 6b82abcd8044 — awaiting tagged release

https://github.com/cryptomator/cryptomator/commit/6b82abcd80449a30b561d823193f9ecea542a625

Weakness Classification(4)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 24× 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-17 19:30 UTCEPSS rescore
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-02 16:38 UTCOSV refresh
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:17 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 29 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 11:00 UTCEG score recompute
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 07:11 UTCEG score recompute
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-12 21:51 UTCEG score recompute
  10. 2026-08-11 06:41 UTCEG score recompute
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-10 06:44 UTCEG score recompute
  13. 2026-08-09 13:46 UTCEPSS rescore
  14. 2026-08-09 06:45 UTCEG score recompute
  15. 2026-08-08 16:37 UTCEPSS rescore
  16. 2026-08-07 17:14 UTCEG score recompute
  17. 2026-08-06 13:46 UTCEPSS rescore
  18. 2026-08-06 01:27 UTCEG score recompute
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-04 15:10 UTCEPSS rescore
  21. 2026-08-04 10:38 UTCEPSS rescore
  22. 2026-08-04 00:35 UTCEG score recompute
  23. 2026-08-03 10:36 UTCEPSS rescore
  24. 2026-08-02 16:11 UTCEG score recompute
  25. 2026-08-01 04:16 UTCEPSS rescore
  26. 2026-07-30 16:28 UTCEPSS rescore
  27. 2026-07-30 01:30 UTCEPSS rescore
  28. 2026-07-27 14:35 UTCEG score recompute
  29. 2026-07-27 14:27 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-32303?
CVE-2026-32303 is a medium vulnerability published on March 20, 2026. 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…
When was CVE-2026-32303 disclosed?
CVE-2026-32303 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-32303 actively exploited?
CVE-2026-32303 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 98.5% of all scored CVEs.
What is the CVSS score of CVE-2026-32303?
CVE-2026-32303 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-32303?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32303, 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-32303

Explore →

Is Your Infrastructure Affected by CVE-2026-32303?

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

Start Free Scan →Browse All CVEs