Vulnerability in Kiteworks Core (CVE-2026-102107)
Summary
Vulnerability in Kiteworks Core (CVE-2026-102107). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Kiteworks Core contains a business logic flaw in a Kiteworks file-request feature allowed an authenticated user to send a request that appeared to originate from another user, because the server did not verify that the requester was authorized to act as the specified account. This could be used to solicit files or information from a recipient under a trusted identity; exploitation requires the feature to be enabled for the attacker's profile and the targeted recipient to act on the request.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-102107 has been found in Kiteworks Core.
Risk of unauthorized operations or information disclosure. CVSS score: 4.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Kiteworks Core CVE-2026-102107" on the vendor's site.
CVE-2026-102107 (Kiteworks Core) — CWE-639 / CVSS v3 4.6
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in Kiteworks Core.
Check the vendor advisory for the affected versions of Kiteworks Core.
Severity: Medium (CVSS 4.6/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Kiteworks Core を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch github.com
- web raw.githubusercontent.com