CVE-2026-102091 json
Kiteworks Secure Data Forms server-side request forgery
published 2026-09-30 39 d ago modified 2026-10-08 32 d ago also EUVD-2026-90372
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
Kiteworks Secure Data Forms before version 9.5.0 is vulnerable to Server-Side Request Forgery that could allow an unauthenticated, remote attacker to make the server issue arbitrary outbound network requests and read back the responses. This could potentially be used to reach internal-only services or other network-restricted resources.
Patch / fix
- Kiteworks Secure Data Forms 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 7.5
Kiteworks multiple vulnerabilities
-
Kiteworks Secure Data Forms <9.5.0affected: vendor fix kiteworks.com
-
Kiteworks Secure Data Forms 9.5.0fixed: 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
- 39 d ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Kiteworks Secure Data Forms
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/kiteworks/security-advisories/security/advisories/GHSA-m8mj-m4fv-jmrh
vendor-advisory
-
raw.githubusercontent.com
/cisagov/CSAF/develop/csaf_files/VA/white/2026/va-26-274-01.json
third-party-advisory, broken-link
Sources
- CVE List CVE-2026-102091
- NVD CVE-2026-102091
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.