{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-102110 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102110 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102110 is a medium-severity missing authorization 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-102110 and fix it if it is affected.\n\nWhat it is: CVE-2026-102110 is a medium-severity missing authorization 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-102110 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-102110/ (Markdown: https://insights.sbomify.com/CVE-2026-102110/index.md)","id":"CVE-2026-102110","markdown":"https://insights.sbomify.com/CVE-2026-102110/index.md","name":"CVE-2026-102110","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Kiteworks Core","requires_auth":"none","summary":"Unauthenticated attackers can repeatedly trigger the privileged activation process during initial setup, disrupting configuration and leaving the appliance incomplete.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"kiteworks","vendor":"accellion"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"An endpoint used during initial appliance setup did not require authentication and did not correctly enforce its intended state precondition, so during the initial activation window an unauthenticated network attacker could repeatedly re-trigger the privileged activation process. This could disrupt setup and leave the appliance in an incompletely configured state. The issue is only reachable while an appliance is being activated for the first time and not yet fully configured.","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":"Missing authentication on a Kiteworks appliance setup function","id":"CVE-2026-102110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"accellion:kiteworks","products":["accellion:kiteworks"],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Kiteworks Core Improper Validation of Specified Quantity in Input","id":"CVE-2026-102111"},"packages":[],"prev":{"headline":"Kiteworks Secure Data Forms SQL injection","id":"CVE-2026-102109"},"products":["Core"],"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-102103","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["Kiteworks"]},"summary":"Unauthenticated attackers can repeatedly trigger the privileged activation process during initial setup, disrupting configuration and leaving the appliance incomplete.","url":"https://insights.sbomify.com/CVE-2026-102110/"}