CVE-2026-102111: Kiteworks improper validation of configurable security-policy setting

CVE-2026-102111 · Severity: medium · CVSS 4.9 · Published 2026-09-30

Kiteworks, a file transfer and data governance platform used by enterprises, has a flaw where authenticated administrators can set a security policy parameter outside its intended range without validation. This causes the related security control to silently stop functioning while appearing enabled in logs and the admin interface, potentially allowing malicious insiders to bypass intended security controls.

Technologies: Kiteworks Core. Vendors: Kiteworks.

Quick answers

Is CVE-2026-102111 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-102111 being exploited in the wild.
How severe is CVE-2026-102111?
Medium severity, with a CVSS score of 4.9, published 30 September 2026.
Which products and versions are affected?
Kiteworks Core before 9.5.0.
Is there a fix for CVE-2026-102111?
A patch was published on 2026-09-30: Patched in version 9.5.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-102111 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-102111?
Check whether you run Kiteworks Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an improper validation of input quantity (CWE-1284) in a configurable security-policy setting in Kiteworks Core. An authenticated administrator with high privileges can set a numeric parameter outside its maximum permitted value, causing the associated security control to never activate while the UI and audit logs continue to show it as enabled. This is a logic bypass that requires admin authentication and network access.

Affected products

  • Kiteworks Core before 9.5.0

Timeline

  • 2026-09-30: disclosed
  • 2026-09-30: patched: Patched in version 9.5.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.