CVE-2026-102113 json
Kiteworks Core Local Privilege Escalation
published 2026-09-30 39 d ago modified 2026-10-07 32 d ago also EUVD-2026-90306
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
A privilege escalation vulnerability in Kiteworks could allow an attacker who has already obtained code execution as an unprivileged backend service account on the appliance to escalate to root. A privileged routine did not safely handle a filesystem path that the lower-privileged account could influence, allowing the attacker to cause a root-owned operation to run arbitrary commands with the highest privileges. Exploitation requires existing local access to that service account.
Patch / fix
- Kiteworks Core 9.5.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa vex VA-26-274-01 updated cvss 7.8
Kiteworks multiple vulnerabilities
-
Kiteworks Core <9.5.0affected: vendor fix kiteworks.com
-
Kiteworks Core 9.5.0fixed: vendor fix kiteworks.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 38 d ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Kiteworks Core
Classification
References
-
github.com
/kiteworks/security-advisories/security/advisories/GHSA-gwj7-wxrr-28v5
vendor-advisory
-
raw.githubusercontent.com
/cisagov/CSAF/develop/csaf_files/VA/white/2026/va-26-274-01.json
third-party-advisory, broken-link
Sources
- CVE List CVE-2026-102113
- NVD CVE-2026-102113
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.