Two Kiteworks Core cluster-management operations did not validate file paths supplied to them, so an attacker holding root on one node of a cluster could write files as root onto another node and cause them to be executed there. Exploitation requires backend root access on a cluster node and a pending software patch present on the target node.
CVE-2026-102141
MEDIUMPre-NVD 6.76.7—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 6.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (below the 1st percentile of EPSS-scored CVEs). 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, secondary
6.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.7Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.7
- EG Score
- 6.7MEDIUMmedium confidence
- EG Risk
- 35EG Risk 35/100CISA SSVC
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 computedSeverity67% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.1%
- EPSS %ILE
- below the 1st
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 30, 2026
Last Modified
October 1, 2026
Advisory Details (1)
Auto-updated Sep 30, 2026Patch available. Sources: github.
github Patch Available
[Core] Kiteworks Core before version 9.5.1 is vulnerable to Privilege Escalation through External Control of File Name or Path · Advisory · kiteworks/security-advisories · GitHub
https://github.com/kiteworks/security-advisories/security/advisories/GHSA-m39v-w8fv-gf3mWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× 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.
- 2026-10-04 07:18 UTCEG score recompute
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 05:46 UTCEG score recompute
- 2026-10-02 04:09 UTCEG score recompute
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-09-30 21:27 UTCEG score recompute
- 2026-09-30 20:26 UTCEG score recompute
- 2026-09-30 20:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-102141?
CVE-2026-102141 is a medium vulnerability published on September 30, 2026. Two Kiteworks Core cluster-management operations did not validate file paths supplied to them, so an attacker holding root on one node of a cluster could write files as root onto another node and cause them to be executed there. Exploitation requires backend root access on a cluster node and a…
When was CVE-2026-102141 disclosed?
CVE-2026-102141 was first published on September 30, 2026, with the most recent update on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102141 actively exploited?
CVE-2026-102141 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102141?
CVE-2026-102141 has a CVSS base score of 6.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102141?
A fix for CVE-2026-102141 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-102141
Is Your Infrastructure Affected by CVE-2026-102141?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.