CVE-2026-102131 json
Kiteworks Email Protection Gateway Improper Handling of Case Sensitivity
published 2026-09-30 39 d ago modified 2026-10-08 31 d ago also EUVD-2026-90286
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
Kiteworks Email Protection Gateway rejected certain configuration settings, but its validation did not recognize every form in which they could be supplied. An authenticated administrator could potentially use an unrecognized form to have a file of their choosing written to the gateway and executed, resulting in code execution as the gateway service account.
Patch / fix
- Kiteworks Email Protection Gateway 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 7.2
Kiteworks multiple vulnerabilities
-
Kiteworks Email Protection Gateway <9.5.0affected: vendor fix kiteworks.com
-
Kiteworks Email Protection Gateway 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
1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Kiteworks Email Protection Gateway
Classification
References
-
github.com
/kiteworks/security-advisories/security/advisories/GHSA-62f6-c955-4fhq
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-102131
- NVD CVE-2026-102131
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.