{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-102141 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102141 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102141 is a medium-severity path traversal vulnerability in Accellion Kiteworks, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102141 and fix it if it is affected.\n\nWhat it is: CVE-2026-102141 is a medium-severity path traversal vulnerability in Accellion Kiteworks, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102141 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-102141/ (Markdown: https://insights.sbomify.com/CVE-2026-102141/index.md)","id":"CVE-2026-102141","markdown":"https://insights.sbomify.com/CVE-2026-102141/index.md","name":"CVE-2026-102141","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Kiteworks Core","requires_auth":"high_privilege","summary":"An attacker with root access on one cluster node can write and execute files as root on another node via unvalidated paths in Kiteworks Core.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"kiteworks","vendor":"accellion"}],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Two Kiteworks Core cluster-management operations did not validate file paths supplied to them, so an attacker holding root on one node of a cluster could write files as root onto another node and cause them to be executed there. Exploitation requires backend root access on a cluster node and a pending software patch present on the target node.","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 Core Privilege Escalation through External Control of File Name or Path","id":"CVE-2026-102141","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"accellion:kiteworks","products":["accellion:kiteworks"],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Kiteworks Core Remote Code Execution through Server-Side Template Injection","id":"CVE-2026-102142"},"packages":[],"prev":{"headline":"Kiteworks Core Insufficient Verification of Data Authenticity","id":"CVE-2026-102140"},"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":"total"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["Kiteworks"]},"summary":"An attacker with root access on one cluster node can write and execute files as root on another node via unvalidated paths in Kiteworks Core.","url":"https://insights.sbomify.com/CVE-2026-102141/"}