Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain admin access to gateway-licensed node
-
DeliveryConfigure connector with internal-targeted URL
-
ExploitServer fetches URL without scheme/destination validation
-
ExecutionRequests reach internal network services
-
ImpactLimited internal information disclosure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires (1) valid authenticated administrator access to a Kiteworks Core node, and (2) the optional, separately-licensed gateway role to be enabled and active on that node - explicitly not a default configuration. Exploitation is limited by these two prerequisites plus the SSRF's constrained impact (limited confidentiality and integrity, no availability impact). Affects Kiteworks Core versions before 9.5.1; fixed in 9.5.1. The connector-URL retrieval performs insufficient validation of URL scheme and destination. |
| Impact | This is a genuinely low-priority SSRF despite being network-reachable. The CVSS vector (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N, base 3.3) is doubly gated: PR:H means the attacker must already be an authenticated administrator, and AC:H reflects that the optional, separately-licensed gateway role must be enabled - a non-default deployment condition explicitly stated in the description. Impact is limited to C:L/I:L/A:N, i.e. probing/limited access to internal services rather than full internal data theft or code execution. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so this is 'no public exploit identified at time of analysis' - consistent with a targeted, low-yield issue rather than a mass-exploitation candidate. SSVC signals are absent from the input. The scenario is realistic (SSRF against internal network services) but the prerequisites (admin credentials AND a licensed, activated gateway role) make it a post-compromise pivot tool, not an initial-access threat. No conflicting signals: the vendor's low score is well-justified by the description. |
| Exploit ScenarioDerived | An attacker who has already obtained administrator credentials on a Kiteworks Core node that has the optional licensed gateway role active configures a connector with a URL pointing at an internal service (e.g. a metadata endpoint or internal admin interface). The server retrieves the URL without validating its scheme or destination, issuing attacker-directed requests into the internal network and returning or acting on limited responses. No public proof-of-concept was identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Server-side request forgery in Kiteworks Core before 9.5.1 lets an authenticated administrator on a node with the separately licensed gateway role enabled supply a connector URL that the server fetches without adequately validating the URL scheme or destination, causing outbound requests to internal network services. Exploitation requires two prerequisites: a valid administrative session (CVSS PR:H) and an active optional gateway role, which is not a default configuration, and the resulting impact is constrained to limited confidentiality and integrity with no availability effect (CVSS 3.3, AC:H). No public exploit code has been identified at time of analysis and there is no evidence of active exploitation; the vendor has released a fixed version, 9.5.1, and the issue was reported through CISA's coordinated disclosure channel.
RemediationAI
Apply the vendor-released fix by upgrading Kiteworks Core to version 9.5.1 or later, which is the exact patched release identified in the advisory data and closes the insufficient-validation logic in connector URL retrieval; consult https://github.com/kiteworks/security-advisories/security/advisories/GHSA-q9w9-c5hj-87jm and the CISA CSAF file at https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/VA/white/2026/va-26-274-01.json for the vendor's upgrade guidance. If immediate upgrade is not possible, the most effective compensating control is to disable the optional gateway role on any node that does not strictly require it - since exploitation is impossible without that role active, this removes the attack surface entirely at the cost of losing the gateway functionality on that node. Where the role must remain enabled, restrict administrative access to a small set of trusted accounts and source IPs (the vector requires PR:H, so reducing who holds admin rights directly reduces exposure), and apply network egress filtering on the Kiteworks host so that server-originated requests to loopback, link-local, and internal RFC 1918 ranges are blocked or forced through an authenticated egress proxy; the trade-off is that legitimate connectors pointing at internal resources may break and will need to be explicitly allowlisted. Monitor connector configuration changes in audit logs as a detection measure while remediation is pending, and note that no public exploit code has been identified at time of analysis, so this is a low-urgency but not zero-urgency fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic server-side request forgery (SSRF) rooted in CWE-918: the Kiteworks Core server acts as the HTTP client on behalf of an administrator-configured connector, and it fails to enforce an allowlist of permitted URL schemes (for example, restricting to https) or to reject destinations that resolve to loopback, link-local, or RFC 1918 internal addresses. Because the fetch is performed by the server itself, an attacker who can set the connector URL can pivot the server's network position to reach internal services that are not otherwise exposed, which is why the CVSS vector rates confidentiality and integrity impact as low (C:L/I:L) rather than high - response data returned to the attacker and any state change on the internal target are bounded by the constrained request format. The attack vector is network (AV:N) but complexity is high (AC:H), reflecting the combination of preconditions needed (active gateway role, crafted URL, reachable internal target), and privileges required is high (PR:H), meaning an authenticated administrator account is mandatory. The affected component is the optional, separately licensed gateway role of Kiteworks Core; the CPE cpe:2.3:a:kiteworks:core:*:*:*:*:*:*:*:* and EUVD data place all Kiteworks Core builds from the initial 0 release through versions prior to 9.5.1 in scope. This specific defect was reported via CISA's coordinated disclosure process (cisa-cg) and tracked as EUVD-2026-90277.
Know when Kiteworks gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
Network-reachable but AC:H (optional licensed gateway role must be active) and PR:H (authenticated admin only); SSRF yields only limited C:L/I:L, no availability impact.
Primary rating from Vendor (cisa-cg).
CVSS VectorVendor: cisa-cg
Lifecycle Timeline
1DescriptionCVE.org
An authenticated administrator on a node with an optional, separately licensed gateway role enabled could supply a connector URL that the server retrieved without sufficient validation of its scheme or destination, causing the server to issue requests to internal network services. Exploitation requires the licensed gateway role to be active.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Unauthenticated attackers who know a target's email address can take over Kiteworks Core accounts that use locally store
Improper certificate-assignment controls in Kiteworks Email Protection Gateway allow a remote, unauthenticated attacker
Stored cross-site scripting in Kiteworks Core (all versions prior to 9.5.0) enables unauthenticated attackers to persist
Authentication bypass in Kiteworks Email Protection Gateway (versions before 9.5.0) lets unauthenticated remote attacker
Server-side request forgery in Kiteworks Email Protection Gateway (versions before 9.5.0) lets a remote, unauthenticated
Server-side request forgery in Kiteworks Email Protection Gateway before 9.5.0 allows a remote, unauthenticated sender t
Unauthenticated server-side request forgery in Kiteworks Email Protection Gateway before version 9.5.0 lets a remote att
Server-side request forgery in Kiteworks Email Protection Gateway before 9.5.0 allows a remote, unauthenticated attacker
Server-side request forgery in Kiteworks Email Protection Gateway (all versions before 9.5.0) lets a remote, unauthentic
Command injection in Kiteworks Core's internal cluster-management function allows an attacker who already has code execu
Sandbox escape in Kiteworks Core's document-conversion feature (CVE-2026-102125, CVSS 8.8) allows code already executing
Authenticated privilege escalation in Kiteworks PDN (the Accellion-line private data network) before version 9.1.0 lets
EUVD-2026-90277
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB