Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain admin access to Kiteworks interface
-
DeliverySubmit crafted request targeting internal service
-
ExploitAppliance issues attacker-directed requests (SSRF, scope change)
-
ExecutionInteract with unreachable internal services
-
ImpactLimited internal info disclosure / state effect
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization CRLF sequence sanitization
|
| Exploitation Conditions | Requires an authenticated administrator account on the Kiteworks Core appliance (PR:H) reaching the affected admin interface; there is no user-interaction requirement (UI:N). Exploitation is limited by the need for administrative privileges and by the fact that, on its own, the flaw only permits issuing/interacting with internal network services (SSRF) and does not achieve code execution - impact chaining would require a separate vulnerability. Affects Kiteworks Core versions before 9.5.1; a vendor patch is available. |
| Impact | All exploitation signals point to a moderate, access-gated issue rather than an urgent one. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L, base 6.6) requires PR:H - an authenticated administrator - which sharply limits the attacker population to already-trusted operators or someone who has first compromised admin credentials. The scope change (S:C) and network vector reflect that the flaw lets the appliance pivot to internal services beyond its intended reach (classic SSRF behavior), but the low C/I/A impacts indicate only partial read/interaction capability, and the description explicitly states this 'did not result in code execution' on its own. No EPSS score, no CISA KEV listing, and no public POC are present in the input, so there is no evidence of active or imminent exploitation. Note a data discrepancy: the assigned CWE-93 (Improper Neutralization of CRLF Sequences) does not match the description, which reads as a Server-Side Request Forgery (CWE-918) issue - verify the weakness classification with the vendor. Net: a real but low-to-medium priority defense-in-depth fix, not a high-real-risk emergency despite the mid-range CVSS. |
| Exploit ScenarioDerived | An authenticated Kiteworks administrator (or an attacker who has obtained admin access) submits a crafted request through the affected admin interface that causes the appliance to issue outbound requests to internal-only network services, enabling interaction with resources not meant to be reachable through that interface. The attacker uses this to probe or interact with internal services for reconnaissance or limited data retrieval; no public exploit is identified at time of analysis, and the flaw does not yield code execution by itself. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Authenticated administrators on Kiteworks Core deployments earlier than 9.5.1 can abuse the administrative interface to make the server issue requests to, and interact with, internal network services that should not be reachable through that interface - a server-side request forgery (SSRF) style weakness with a scope change (S:C) that still carries a moderate 6.6 base score. Exploitation is gated behind high privileges (PR:H) and, as the vendor and our assessment both note, does not by itself achieve remote code execution; meaningful impact would require chaining with a separate flaw. No public exploit has been identified at time of analysis, but a vendor patch is available in Kiteworks Core 9.5.1, so the primary risk is to organizations that expose the admin plane to untrusted networks or allow unrestricted egress from the appliance.
RemediationAI
Upgrade Kiteworks Core to version 9.5.1 or later - this is the vendor-released patch and the only complete fix, documented in the Kiteworks advisory GHSA-h97r-j99c-q8xc and referenced by the CISA CSAF advisory VA-26-274-01. Where immediate upgrade is not possible, apply compensating controls that target the two things this bug needs: a high-privileged admin session and reachable internal services. First, restrict access to the Kiteworks administrative interface to a dedicated management network or VPN and enforce MFA plus least-privilege admin roles, accepting that this limits administrator convenience and remote management. Second, enforce strict egress filtering from the appliance so it can only reach the specific external endpoints and integrations it legitimately requires; this breaks the SSRF payoff by making internal targets unreachable, at the cost of potentially disrupting undocumented or ad-hoc integrations that must then be allowlisted. Third, segment the Kiteworks host from management, metadata and internal API networks so even a successful request cannot reach sensitive services, which adds architectural complexity but contains the blast radius. Finally, review Kiteworks audit and proxy logs for outbound requests originating from the admin interface toward RFC1918 addresses or cloud metadata endpoints, since such requests may indicate prior exploitation attempts.
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 affected component is Kiteworks Core (CPE cpe:2.3:a:kiteworks:core), the secure file transfer and content-governance platform formerly known as Accellion Kiteworks, and the flaw is catalogued under CWE-93 (Improper Neutralization of CRLF Sequences, i.e. CRLF/header injection). In practice the CVE description describes the observable outcome as the server being coerced into issuing requests to and interacting with internal services, which is consistent with attacker-controlled input - potentially including injected CR/LF sequences - flowing into the construction of an outbound HTTP request from the administrative interface. The provider's own description confirms that this alone did not result in code execution, so the primitive is best understood as an SSRF/request-manipulation capability rather than a memory-corruption or deserialization bug. The CVSS vector (AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L) indicates the trigger comes over the network with no user interaction but requires a high-privileged administrator account, and that successful exploitation crosses a security boundary (S:C) while individually producing only low confidentiality, integrity and availability impact. The internal-services reachability is what makes this worth tracking: it can be used to map or probe otherwise unreachable management endpoints, metadata services or API backends, and the informational or integrity gain from those interactions may feed a follow-on exploit chain.
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:L/PR:H/UI:N/S:C/C:L/I:L/A:L
Authenticated admin required (PR:H) over the network with low complexity; SSRF reaches out-of-scope internal services (S:C) with only limited confidentiality/integrity/availability impact.
Primary rating from Vendor (cisa-cg).
CVSS VectorVendor: cisa-cg
Lifecycle Timeline
1DescriptionCVE.org
An authenticated administrator could cause the server to issue requests to, and interact with, internal network services that are not meant to be reachable through this interface. On its own this did not result in code execution.
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
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-90381
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB