{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19039 exists.","fix":"No fix has been published for CVE-2026-19039 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19039 is a medium-severity command injection vulnerability in Kino-Kafkaesque ssh-mcp-server, published on 6 Aug 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-19039 and fix it if it is affected.\n\nWhat it is: CVE-2026-19039 is a medium-severity command injection vulnerability in Kino-Kafkaesque ssh-mcp-server, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19039 exists.\n\nAffected product: Kino-Kafkaesque ssh-mcp-server. 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-19039/ (Markdown: https://insights.sbomify.com/CVE-2026-19039/index.md)","id":"CVE-2026-19039","markdown":"https://insights.sbomify.com/CVE-2026-19039/index.md","name":"CVE-2026-19039","record":{"aliases":["GHSA-26qx-2c8w-xjfx"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SSH MCP server","requires_auth":"low_privilege","summary":"Local attackers can inject commands via SSH arguments in ssh-mcp-server, though maintainers argue the tool is intended for trusted local use.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A vulnerability was detected in Kino-Kafkaesque ssh-mcp-server up to 8ebbbb99b26f80ff6162fe00957c6dec73fbc5a5. Impacted is the function ssh_exec of the file src/index.ts of the component SSH Command Handler. Performing a manipulation of the argument host/username results in command injection. The attack requires a local approach. The actual existence of this vulnerability is currently in question. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project maintainer explains: \"The intended threat model is that this MCP server is a local/trusted tool for an agent to execute commands over SSH, so callers already have meaningful execution capability through the exposed shell.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Kino-Kafkaesque ssh-mcp-server SSH index.ts ssh_exec command injection","id":"CVE-2026-19039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"MissionSquad mcp-api dcrClients.ts server-side request forgery","id":"CVE-2026-19040"},"packages":[],"prev":{"headline":"MonomythDevelopment la-forge-mcp screenshot_element Tool index.ts screenshotElement path traversal","id":"CVE-2026-19038"},"products":["ssh-mcp-server"],"published":"2026-08-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-06","vendors":["Kino-Kafkaesque"]},"summary":"Local attackers can inject commands via SSH arguments in ssh-mcp-server, though maintainers argue the tool is intended for trusted local use.","url":"https://insights.sbomify.com/CVE-2026-19039/"}