CVE-2026-102111 json
Kiteworks Core Improper Validation of Specified Quantity in Input
published 2026-09-30 39 d ago modified 2026-10-07 32 d ago also EUVD-2026-90308
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
Kiteworks did not enforce the maximum permitted value for a configurable security-policy setting. An authenticated administrator could set this value outside its intended range so that the associated control never activated, while the control continued to appear enabled in the administrative interface and audit log, allowing it to be silently rendered ineffective.
Patch / fix
- Kiteworks Core 9.5.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa vex VA-26-274-01 updated cvss 4.9
Kiteworks multiple vulnerabilities
-
Kiteworks Core <9.5.0affected: vendor fix kiteworks.com
-
Kiteworks Core 9.5.0fixed: vendor fix kiteworks.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 38 d ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Kiteworks Core
Classification
- Weakness
-
- CWE-1284 Improper Validation of Specified Quantity in Input
References
-
github.com
/kiteworks/security-advisories/security/advisories/GHSA-4r97-hch3-g2f9
vendor-advisory
-
raw.githubusercontent.com
/cisagov/CSAF/develop/csaf_files/VA/white/2026/va-26-274-01.json
third-party-advisory, broken-link
Sources
- CVE List CVE-2026-102111
- NVD CVE-2026-102111
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.