CVE-2026-102136

Kiteworks Core Command Execution through Configuration Injection

Published Sep 30, 2026 CVSS 3.1 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
In multi-node deployments, an attacker who had already obtained code execution on one appliance node could submit a value through an internal cluster interface that was written into monitoring configuration on another node without sufficient validation, potentially allowing OS commands to be executed there. Execution was limited to an unprivileged service account on that node.

Analysis

AI-generated

Technical impact

In a multi‑node deployment of Kiteworks, an attacker who has local code execution on one node can submit arbitrary configuration values to an internal cluster interface. These values are written to monitoring configuration on another node without proper validation, allowing OS commands to be executed under an unprivileged service account. The vulnerability is a form of configuration injection that can lead to further compromise or lateral movement within the cluster.

Affected Systems

The affected product is Kiteworks Core, any multi‑node deployment using the internal cluster interface. Version information is not provided in the advisory, so all current releases of the Core product could be impacted.

Risk and Exploitability

The CVSS score of 6.3 indicates a moderate severity. Because the attack requires existing code execution on a node and access to the internal cluster interface, it is not a null‑click vulnerability and its overall exploitation probability is moderate. The advisory notes that no KEV listing exists and the EPSS value is not available. Consequently, the threat is most pronounced when an attacker has already compromised a node in the cluster; no public exploit has been reported at this time.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor patch or update to the latest release of Kiteworks Core once available.
  • Restrict the internal cluster interface so that only trusted nodes and authenticated clients can submit configuration changes.
  • Enforce strict input validation on all configuration parameters to reject non‑shell‑command content and limit allowed values.

Generated by OpenCVE AI on September 30, 2026 at 22:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Accellion
Accellion kiteworks
CPEs cpe:2.3:a:accellion:kiteworks:*:*:*:*:*:*:*:*
Vendors & Products Accellion
Accellion kiteworks
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Kiteworks
Kiteworks core
Vendors & Products Kiteworks
Kiteworks core
Type Values Removed Values Added
Description In multi-node deployments, an attacker who had already obtained code execution on one appliance node could submit a value through an internal cluster interface that was written into monitoring configuration on another node without sufficient validation, potentially allowing OS commands to be executed there. Execution was limited to an unprivileged service account on that node.
Title Kiteworks Core Command Execution through Configuration Injection
Weaknesses CWE-93
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L'}

Weaknesses
  • CWE-93

    Improper Neutralization of CRLF Sequences ('CRLF Injection')

Sources

Status
PUBLISHED
Assigner
cisa-cg
Published
Updated
Oct 1, 2026, 1:37 PM
Reserved
Sep 28, 2026, 5:39 PM
Status
Analyzed
Published
Sep 30, 2026, 9:17 PM
Modified
Oct 13, 2026, 11:59 AM