CVE-2026-102101 json
Kiteworks Core deserialization of untrusted data
published 2026-09-30 39 d ago modified 2026-10-07 32 d ago also EUVD-2026-90276
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
Kiteworks Core before version 9.5.0 is vulnerable to Deserialization of Untrusted Data. A deserialization weakness in Kiteworks Core could, under certain conditions, allow crafted data to be deserialized unsafely, potentially resulting in remote code execution on the appliance. Exploitation depends on an attacker first being able to influence the affected data, so this issue is not exploitable on its own.
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 8.1
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
- total
- Assessed
- 38 d ago
Exploit prediction
0.94% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- Kiteworks Core
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/kiteworks/security-advisories/security/advisories/GHSA-x5hx-fgrp-prvf
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-102101
- NVD CVE-2026-102101
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.