Core: Improper Isolation or Compartmentalization
CVE-2026-102125 is a high-severity improper isolation or compartmentalization vulnerability in Core from Kiteworks, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 9.5.0 as the first without the flaw, so updating Core to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.39% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Core to 9.5.0 or a later version.
- Update Kiteworks to 9.5.0 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Kiteworks | Core | before 9.5.0 | 9.5.0 |
| Accellion | Kiteworks | before 9.5.0 | 9.5.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA.
Official description
The sandbox that isolates document conversion on a Kiteworks appliance did not fully confine the code running inside it. Code already executing within that sandbox could potentially escape its confinement and act with the privileges of the service account that runs the application, which could allow an attacker in that position to read or modify application data and configuration, or to disrupt the service on the affected appliance.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Isolation or Compartmentalization
The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.
How developers prevent this class of flaw
- Break up privileges between different modules, objects, or entities. Minimize the interfaces between modules and require strong access control between them.
More Improper Isolation or Compartmentalization vulnerabilities (CWE-653)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
Other vulnerabilities in Core
- 9.3 Critical severity
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
- 8.1 High severity
- 7.4 High severity
Recent Improper Isolation or Compartmentalization vulnerabilities
- 9.6 Critical severity
- 7.6 High severity
- 8.3 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.