Kiteworks Core CVE-2026-102096

Requires an authenticated Kiteworks administrator account with access to the configuration-package upload feature of the appliance's admin interface (PR:H). Exploitation is performed by supplying a crafted configuration package whose contents bypass the insufficient validation and are processed into OS command execution. Limiting factors: administrator-level authentication is mandatory (no unauthenticated path), no user interaction by a second party is needed (UI:N), and it affects Kiteworks Core appliances running versions before 9.5.0. The high-privilege prerequisite is the dominant constraint - this is realistically a post-compromise or malicious/compromised-admin scenario rather than opportunistic remote exploitation.

The vendor CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2 High) is internally consistent and I concur with it. This is genuine OS command injection (CWE-78) yielding full C:H/I:H/A:H impact on the appliance, but it is strongly gated by PR:H: only an authenticated administrator can upload the configuration package that triggers arbitrary command execution. That gating is what separates this from a critical bug - the pre-condition (admin access) largely presupposes the attacker already controls the appliance's management plane. 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: the network vector is consistent with a web-based admin upload interface, and PR:H matches the description's 'authenticated administrator' language. Real-world priority is LOW-to-MEDIUM: high technical impact but a narrow, high-privilege prerequisite and no evidence of active or automated exploitation. Primary residual risk is as a post-authentication privilege/persistence step (admin → root/host command execution) or when admin credentials are phished, reused, or the admin account is a lower-trust delegated role.

An attacker who has obtained Kiteworks administrator credentials (via phishing, credential reuse, or an insider) logs into the appliance's admin console and uploads a maliciously crafted configuration package. Because the package contents are not sufficiently validated before processing, embedded payload data is passed to the underlying OS, executing arbitrary commands potentially with elevated privileges. No public exploit code was identified at the time of analysis.