CVE-2026-102134

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (10th 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
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: None knownExposed services: Not assessed

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

Kiteworks Core did not apply its gateway-level API security controls to every request authenticated through the platform's central authentication service. An authenticated user could reach REST API functionality over a request path on which those controls, including enforcement of signed-out and revoked sessions, were not applied.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 7, 2026

Advisory Details (1)

Auto-updated Sep 30, 2026
No fix on record yet. Sources: github.
githubMentions a patch (unverified)

[Core] Kiteworks Core before version 9.5.1 is vulnerable to Unprotected Alternate Channel · Advisory · kiteworks/security-advisories · GitHub

https://github.com/kiteworks/security-advisories/security/advisories/GHSA-8q58-vrwm-jxhq

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 19× 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-09 20:06 UTCEPSS rescore
  2. 2026-10-09 18:50 UTCEG score recompute
  3. 2026-10-08 17:11 UTCEPSS rescore
  4. 2026-10-08 16:49 UTCEG score recompute
  5. 2026-10-07 23:47 UTCEPSS rescore
  6. 2026-10-07 00:32 UTCEG score recompute
  7. 2026-10-06 15:17 UTCEPSS rescore
  8. 2026-10-05 22:27 UTCEG score recompute
  9. 2026-10-05 17:42 UTCEPSS rescore
  10. 2026-10-04 23:21 UTCEPSS rescore
  11. 2026-10-03 18:26 UTCEG score recompute
  12. 2026-10-03 14:25 UTCEPSS rescore
  13. 2026-10-02 16:23 UTCEG score recompute
  14. 2026-10-01 19:49 UTCEPSS rescore
  15. 2026-10-01 14:22 UTCEG score recompute
  16. 2026-10-01 13:42 UTCEG score recompute
  17. 2026-09-30 21:27 UTCEG score recompute
  18. 2026-09-30 20:26 UTCEG score recompute
  19. 2026-09-30 20:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102134?
CVE-2026-102134 is a medium vulnerability published on September 30, 2026. Kiteworks Core did not apply its gateway-level API security controls to every request authenticated through the platform's central authentication service. An authenticated user could reach REST API functionality over a request path on which those controls, including enforcement of signed-out and…
When was CVE-2026-102134 disclosed?
CVE-2026-102134 was first published on September 30, 2026, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102134 actively exploited?
CVE-2026-102134 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102134?
CVE-2026-102134 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102134?
No fix for CVE-2026-102134 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-102134?

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

Book a Demo →Browse All CVEs