Core: Incorrect Privilege Assignment
CVE-2026-102129 is a high-severity incorrect privilege assignment vulnerability in Core from Kiteworks, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists version 9.5.1 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.84% chance of exploitation within 30 days, higher than 58% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Core to 9.5.1 or a later version.
- Update Kiteworks to 9.5.1 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Kiteworks | Core | before 9.5.1 | 9.5.1 |
| Accellion | Kiteworks | before 9.5.1 | 9.5.1 |
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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- 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:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
Official description
A user-provisioning interface in Kiteworks Core did not verify that the requesting administrator was entitled to grant the role being assigned. An administrator whose delegated permissions covered role changes alone could therefore raise an account to full system-administrator privileges.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Privilege Assignment
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
More Incorrect Privilege Assignment vulnerabilities (CWE-266)
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).
References
Other vulnerabilities in Core
- 9.3 Critical severity
- 7.2 High severity
- 7.2 High severity
- 8.1 High severity
- 8.8 High severity
- 7.4 High severity
Recent Incorrect Privilege Assignment vulnerabilities
- 9.3 Critical severity
- 7.3 High severity
- 8.8 High severity
- 7.3 High severity
- 8.8 High severity
- 7.3 High severity
Spotted an error? Tell us.