Kiteworks Core Path Traversal

Answer in brief

CVE-2026-102123 records a High severity (CVSS 7.4) vulnerability in Kiteworks Core Path Traversal. 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: High · CVSS 7.4
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.4. 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.0	9.5.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for Kiteworks/Core.
Review the reported fix. Update Kiteworks/Core to 9.5.0 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

A Kiteworks appliance setup interface did not confine a user-supplied file path to its intended directory, which could allow an unauthenticated attacker to write a file to any location writable by the affected service account, potentially compromising the integrity of the appliance or rendering it unavailable until an operator intervenes. Exploitation requires network access to the affected interface, which is not reachable on a fully configured appliance in its default configuration; reaching it depends on either the transient window while an appliance is first being provisioned or a non-default appliance configuration.

Quoted source text, attributed separately from HOL analysis.