Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain shell as low-priv service account
-
DeliveryPlant symlink for root-run operation
-
ExploitTrigger privileged link-following (CWE-59)
-
ExecutionEscalate to root on appliance
-
ImpactFull appliance compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Exploitation Conditions | Requires the attacker to ALREADY hold local command execution as the low-privileged Kiteworks service account on the appliance (PR:L, AV:L) - this is not remotely reachable on its own and is realistically a second-stage escalation following a separate initial-access vulnerability. Given that foothold, no user interaction, no extra credentials, and no non-default configuration are required: the flaw is a link-following (CWE-59) weakness in a root-privileged operation on the Kiteworks Core appliance. The principal limiting factor is the prerequisite service-account foothold; the principal risk is that success grants full root control of the appliance. |
| Impact | This is a genuine but chained/secondary-priority issue rather than a top-of-queue emergency. The CVSS 3.1 vector (7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) is internally consistent with the description: exploitation is LOCAL (AV:L), requires an already-authenticated low-privileged foothold (PR:L), needs no user interaction, and yields full compromise of the appliance (C:H/I:H/A:H via root). The high base score is driven by the total-compromise impact, not by ease of initial reach - the AV:L/PR:L prerequisite means the attacker must ALREADY have a shell as the service account before this bug is useful. No EPSS score, no CISA KEV listing, and no public POC were provided, so exploitation status is: no public exploit identified at time of analysis. There is no signal conflict - all signals point to a real-but-gated local escalation. The primary risk multiplier is that on a hardened appliance the whole security model rests on the service account NOT being root; this bug collapses that boundary, so it is a valuable second stage in any chain that first achieves service-account code execution on a Kiteworks node (e.g. the SSRF/RCE/deserialization siblings in the same va-26-274-01 batch). |
| Exploit ScenarioDerived | An attacker who has already obtained command execution as the low-privileged Kiteworks service account - for example by chaining a separate application-level RCE or upload flaw on the appliance - abuses a link-following (CWE-59) weakness in a root-owned/root-executed operation to have a privileged process act on an attacker-controlled symlink, resulting in root on the appliance. No user interaction and no additional credentials are required once the local foothold exists. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Local privilege escalation in Kiteworks Core allows an attacker who already holds a shell under a low-privileged service account to elevate to root on the appliance, gaining complete control of the system and the sensitive content it brokers. The weakness is a link-following issue (CWE-59) in a root-privileged operation, reachable with local access as the service account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), no user interaction, and no non-default configuration, making it a realistic second-stage escalation after a separate initial-access compromise. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the CVE is not associated with a KEV listing; the primary limiting factor is the prerequisite service-account foothold, while the primary risk is full root compromise of the appliance.
RemediationAI
Patch status is not independently confirmed by the supplied data, so the primary action is to consult the vendor advisory GHSA-8pmh-222g-6j48 (and the linked CISA CSAF document va-26-274-01) for the exact fixed Kiteworks Core build and upgrade to that release through the standard vendor-supported appliance update process; do not attempt manual filesystem-level fixes on an appliance, as unsupported changes can void support and break integrity checks. Until the fixed build is applied, the highest-value compensating controls all target the prerequisite foothold rather than the link-following primitive itself: remove or disable interactive shell access for the low-privileged Kiteworks service account (for example by setting its shell to nologin and removing it from any privileged groups), accepting the trade-off that some support and diagnostic workflows may require a temporary, audited re-enable; restrict administrative and SSH access to a dedicated management network or jump host so that obtaining any local shell is significantly harder; and monitor for creation of symbolic links in root-writable directories or for service-account processes touching paths outside their normal working set, understanding that such detections are heuristic and will generate false positives in environments with legitimate automation. Because the escalation requires a pre-existing local foothold, priority should be given to hardening and patching the initial-access surface of the appliance in parallel, and to reviewing logs for evidence that service-account code execution has already been obtained.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Kiteworks Core is the underlying secure file transfer / enterprise file-sharing platform that runs on a hardened appliance, and the affected component is identified by the CPE cpe:2.3:a:kiteworks:core:*:*:*:*:*:*:*:*, indicating the platform itself rather than a plug-in or module. The root cause class is CWE-59, Improper Link Resolution Before File Access ('link following'): a privileged routine performs a file operation on a path that an attacker with local, lower-privileged access can influence by pre-positioning a symbolic link or similar filesystem reparse point, causing the root-owned process to read, write, or execute an attacker-chosen target. Because the CVSS vector shows AV:L/PR:L with Scope Unchanged and High Confidentiality, Integrity, and Availability impact, the flaw neither crosses a security authority boundary nor requires remote reachability - the attacker must already execute code as the low-privileged Kiteworks service account, but from that foothold the escalation is deterministic and yields root-level read/write/execute on the appliance. This places the issue in the classic 'post-exploitation' category: it does not by itself provide an entry point, but it substantially raises the impact of any other bug that yields service-account code execution.
Know when Kiteworks gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local vector and prior low-priv service-account foothold give AV:L/PR:L; deterministic link-following gives AC:L; escalation to root yields full C:H/I:H/A:H with no scope change.
Primary rating from Vendor (cisa-cg).
CVSS VectorVendor: cisa-cg
Lifecycle Timeline
2DescriptionCVE.org
A local privilege escalation vulnerability in Kiteworks could have allowed an attacker with an existing shell under a low-privileged service account to escalate to root privileges on the appliance.
Technical POC Analysis
Evidence basis: this analysis rests on advisory GHSA-8pmh-222g-6j48 only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Kiteworks Core (CVE-2026-102118) contains a high-severity local privilege escalation vulnerability that allows an authenticated attacker with a low-privileged service account to gain root control of the appliance. This could lead to complete compromise of sensitive content brokered by the platform, affecting data confidentiality and integrity. No public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, making immediate compensating controls essential for organizations using this product.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict and monitor service account shell access, enforce least privilege, harden file system permissions and mount options (nosuid/noexec), deploy SELinux/AppArmor, and conduct regular audits for signs of privilege escalation.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Unauthenticated attackers who know a target's email address can take over Kiteworks Core accounts that use locally store
Improper certificate-assignment controls in Kiteworks Email Protection Gateway allow a remote, unauthenticated attacker
Stored cross-site scripting in Kiteworks Core (all versions prior to 9.5.0) enables unauthenticated attackers to persist
Authentication bypass in Kiteworks Email Protection Gateway (versions before 9.5.0) lets unauthenticated remote attacker
Server-side request forgery in Kiteworks Email Protection Gateway (versions before 9.5.0) lets a remote, unauthenticated
Server-side request forgery in Kiteworks Email Protection Gateway before 9.5.0 allows a remote, unauthenticated sender t
Unauthenticated server-side request forgery in Kiteworks Email Protection Gateway before version 9.5.0 lets a remote att
Server-side request forgery in Kiteworks Email Protection Gateway before 9.5.0 allows a remote, unauthenticated attacker
Server-side request forgery in Kiteworks Email Protection Gateway (all versions before 9.5.0) lets a remote, unauthentic
Command injection in Kiteworks Core's internal cluster-management function allows an attacker who already has code execu
Sandbox escape in Kiteworks Core's document-conversion feature (CVE-2026-102125, CVSS 8.8) allows code already executing
Authenticated privilege escalation in Kiteworks PDN (the Accellion-line private data network) before version 9.1.0 lets
EUVD-2026-90301
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB