CVE-2026-102101

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (21st 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
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Kiteworks Core before version 9.5.0 is vulnerable to Deserialization of Untrusted Data. A deserialization weakness in Kiteworks Core could, under certain conditions, allow crafted data to be deserialized unsafely, potentially resulting in remote code execution on the appliance. Exploitation depends on an attacker first being able to influence the affected data, so this issue is not exploitable on its own.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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 computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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, 2026
Patch available. Sources: github.
github Patch Available

[Core] Kiteworks Core before version 9.5.0 is vulnerable to Deserialization of Untrusted Data · Advisory · kiteworks/security-advisories · GitHub

https://github.com/kiteworks/security-advisories/security/advisories/GHSA-x5hx-fgrp-prvf

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 10× 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-10-03 16:28 UTCEG score recompute
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-03 03:59 UTCEG score recompute
  4. 2026-10-02 02:54 UTCEG score recompute
  5. 2026-10-01 19:49 UTCEPSS rescore
  6. 2026-10-01 14:22 UTCEG score recompute
  7. 2026-10-01 13:42 UTCEG score recompute
  8. 2026-09-30 21:27 UTCEG score recompute
  9. 2026-09-30 20:26 UTCEG score recompute
  10. 2026-09-30 20:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102101?
CVE-2026-102101 is a high vulnerability published on September 30, 2026. Kiteworks Core before version 9.5.0 is vulnerable to Deserialization of Untrusted Data. A deserialization weakness in Kiteworks Core could, under certain conditions, allow crafted data to be deserialized unsafely, potentially resulting in remote code execution on the appliance. Exploitation depends…
When was CVE-2026-102101 disclosed?
CVE-2026-102101 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-102101 actively exploited?
CVE-2026-102101 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102101?
CVE-2026-102101 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102101?
A fix for CVE-2026-102101 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-102101

Explore →

Is Your Infrastructure Affected by CVE-2026-102101?

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

Book a Demo →Browse All CVEs