Kiteworks Core Insufficient Verification of Data Authenticity (CVE-2026-102140) | HOL Guard CVE

Medium · CVSS 4.9CVE-2026-102140

Kiteworks Core Insufficient Verification of Data Authenticity

Answer in brief

CVE-2026-102140 records a Medium severity (CVSS 4.9) vulnerability in Kiteworks Core Insufficient Verification of Data Authenticity. 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 4.9
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 4.9. 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

An authenticated administrator could initiate an administrative import using a file whose contents were not fully verified, because the import validated only the file's header rather than the complete file. This could allow unverified or forged content to be accepted and processed, affecting the integrity of the imported data.

Quoted source text, attributed separately from HOL analysis.