CVE-2026-102095: Kiteworks Email Protection Gateway · Server-Side Request Forgery (SSRF)
Affects Kiteworks Email Protection GatewaySource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 9.5.0 as a priority.
Data as of 14 Nov 2026, 20:43 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.5.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade Kiteworks Email Protection Gateway to 9.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| KiteworksEmail Protection Gateway | Affected
| Fixed in
|
AI-suggested
A fixed version 9.5.0 is available that addresses this vulnerability. Users should upgrade Kiteworks Email Protection Gateway to version 9.5.0 or later to remediate this issue. No other mitigation steps are indicated in the provided data.
Description
Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Server-Side Request Forgery. Kiteworks Email Protection Gateway performed server-side fetches of URLs contained in the message content it processed, without adequately restricting the fetch destination. A remote, unauthenticated sender could craft a message that caused the gateway to issue requests to internal services and cloud instance metadata endpoints and return the responses, potentially disclosing sensitive internal data and, depending on the internal service reached, affecting its state.