Kiteworks Core Command Execution through Configuration Injection (CVE-2026-102136) | HOL Guard CVE

Medium · CVSS 6.3CVE-2026-102136

Kiteworks Core Command Execution through Configuration Injection

Answer in brief

CVE-2026-102136 records a Medium severity (CVSS 6.3) vulnerability in Kiteworks Core Command Execution through Configuration Injection. The current sources do not mark it as known exploited. The current feed maps Kiteworks/Core (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 30, 2026Updated Sep 30, 2026Source checked Sep 30, 2026First seen by HOL Sep 30, 2026Material review Sep 30, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Kiteworks/Core (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Kiteworks/Coregeneric	>=0 <9.5.1	9.5.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for Kiteworks/Core.
Review the reported fix. Update Kiteworks/Core to 9.5.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 30, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.