CVE.org (no NVD analysis yet)· CNA cisa-cg

CVE-2026-102111: Kiteworks Core Improper Validation of Specified Quantity in Input

Noroxi assessment

Priority: Monitor (action score 19/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.9 · v3.1—No exploit No fix recorded

EUVD-2026-90308

Published: Sep 30, 2026
Updated: Oct 7, 2026
EPSS: 0.2% · 11th percentile
CWE: CWE-1284

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 19 / 40 · 4.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · cisa-cg: 4.9; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
accellion	kiteworks	cpe:2.3:a:accellion:kiteworks

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

accellion kiteworksbefore 9.5.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (cisa-cg). Independent of NVD's CPE analysis and usually ahead of it.

Kiteworks Core
- 9.5.0not affected
- before 9.5.0affected

Same product

accellion: all records

Other highest-scoring records for the same primary product.

CVE-2021-31586Accellion Kiteworks before 7.4.0 allows an authenticated user to perform SQL Injection via LDAPGroup Search.
48Plan
CVE-2026-102115Kiteworks Core Authentication Bypass in the Password Reset Workflow
39Monitor
CVE-2026-102149Kiteworks Email Protection Gateway Improper Access Control
37Monitor

Published before and after this one in the same product

← EarlierCVE-2026-102109Sep 30, 2026 · Kiteworks Secure Data Forms SQL injection
28Monitor
← EarlierCVE-2026-102110Sep 30, 2026 · Missing authentication on a Kiteworks appliance setup function
23Monitor
Later →CVE-2026-102112Sep 30, 2026 · Kiteworks Core Local Privilege Escalation
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).