Skip to content
Fencer Vulns
critical 9.1

CVE-2026-102102 json

Kiteworks Email Protection Gateway server-side request forgery

published 2026-09-30 39 d ago modified 2026-10-08 31 d ago also EUVD-2026-90282

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Server-Side Request Forgery (SSRF). A server-side request forgery (SSRF) weakness in Kiteworks Email Protection Gateway could allow a remote, unauthenticated attacker to induce the gateway to issue crafted requests to internal or otherwise unintended network destinations. The requests are triggered while the gateway retrieves an issuer certificate in an inbound message. Depending on the services reachable from the gateway, this could disclose sensitive internal information or disrupt gateway operation.

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 9.1

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
yes
Technical impact
partial
Assessed
38 d ago

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Affected products

  • Kiteworks Email Protection Gateway

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

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.