Skip to content
Fencer Intel
high 7.2

CVE-2026-102131 json

Kiteworks Email Protection Gateway Improper Handling of Case Sensitivity

published last mo. modified last mo. 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

Is CVE-2026-102131 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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.0
    affected: vendor fix kiteworks.com
  • Kiteworks Email Protection Gateway 9.5.0
    fixed: 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
last mo.

Exploit prediction

1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

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

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-178 Improper Handling of Case Sensitivity

References

Sources

Fencer Intel 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.