{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-102103 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102103 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102103 is a critical server-side request forgery vulnerability in Accellion Kiteworks, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102103 and fix it if it is affected.\n\nWhat it is: CVE-2026-102103 is a critical server-side request forgery vulnerability in Accellion Kiteworks, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102103 in the wild and no public exploit code.\n\nAffected product: Accellion Kiteworks. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102103/ (Markdown: https://insights.sbomify.com/CVE-2026-102103/index.md)","id":"CVE-2026-102103","markdown":"https://insights.sbomify.com/CVE-2026-102103/index.md","name":"CVE-2026-102103","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Email Protection Gateway","requires_auth":"none","summary":"Unauthenticated attackers can trigger SSRF via CRL retrieval, potentially exposing internal data or disrupting the email gateway service.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"kiteworks","vendor":"accellion"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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 a certificate revocation list in an inbound message. Depending on the services reachable from the gateway, this could disclose sensitive internal information or disrupt gateway operation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Kiteworks Email Protection Gateway server-side request forgery","id":"CVE-2026-102103","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"accellion:kiteworks","products":["accellion:kiteworks"],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Kiteworks Email Protection Gateway server-side request forgery","id":"CVE-2026-102104"},"packages":[],"prev":{"headline":"Kiteworks Email Protection Gateway server-side request forgery","id":"CVE-2026-102102"},"products":["Email Protection Gateway"],"published":"2026-09-30","related":[{"cvss_score":9.8,"headline":"Kiteworks Core Authentication Bypass in the Password Reset Workflow","id":"CVE-2026-102115","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":9.4,"headline":"Kiteworks Email Protection Gateway Improper Access Control","id":"CVE-2026-102149","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":9.3,"headline":"Kiteworks Core Administrative Account Takeover through Stored Cross-site Scripting (XSS)","id":"CVE-2026-102147","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":9.1,"headline":"Kiteworks Email Protection Gateway server-side request forgery","id":"CVE-2026-102095","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":9.1,"headline":"Kiteworks Email Protection Gateway server-side request forgery","id":"CVE-2026-102102","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":9.1,"headline":"Kiteworks Email Protection Gateway server-side request forgery","id":"CVE-2026-102104","kev_date_added":null,"published":"2026-09-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["Kiteworks"]},"summary":"Unauthenticated attackers can trigger SSRF via CRL retrieval, potentially exposing internal data or disrupting the email gateway service.","url":"https://insights.sbomify.com/CVE-2026-102103/"}