CVE-2025-53818: github-kanban-mcp-server Command Injection vulnerability
GitHub Kanban MCP Server is a Model Context Protocol (MCP) server for managing GitHub issues in Kanban board format and streamlining LLM task management. Version 0.3.0 of the MCP Server is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation. The MCP Server exposes the tool addcomment which relies on Node.js child process API exec to execute the GitHub (gh) command, is an unsafe and vulnerable API if concatenated with untrusted user input. As of time of publication, no known patches are available.
Other sources
The MCP Server at https://github.com/Sunwood-ai-labs/github-kanban-mcp-server/ is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation.
Vulnerable tool
The MCP Server exposes the tool addcomment which relies on Node.js child process API exec to execute the GitHub (gh) command, is an unsafe and vulnerable API if concatenated with untrusted user input.
Data flows from the tool definition here which takes in args.issuenumber and calls handleAddComment() in this definitino that uses exec in an insecure way.
Vulnerable line of code: https://github.com/Sunwood-ai-labs/github-kanban-mcp-server/blob/main/src/handlers/comment-handlers.ts#L8-L23
js export async function handleAddComment(args: { repo: string; issuenumber: string; body: string; state?: 'open' | 'closed'; }): Promise<ToolResponse> { const tempFile = 'commentbody.md';
try { // ステータスの変更が指定されている場合は先に処理 if (args.state) { try { const command = args.state === 'closed' ? 'close' : 'reopen'; await execAsync( gh issue ${command} ${args.issuenumber} --repo ${args.repo} );
Exploitation Proof of Concept
When LLMs are tricked through prompt injection (and other techniques and attack vectors) to call the tool with input that uses special shell characters such as ; rm -rf /tmp;# (be careful actually executing this payload) and other payload variations, the full command-line text will be interepted by the shell and result in other commands except of ps executing on the host running the MCP Server.
Reference example from prior security research on this topic, demonstrating how a similarly vulnerable MCP Server connected to Cursor is abused with prompt injection to bypass the developer's intended command:
!Cursor defined MCP Server vulnerable to command injection
Impact
User initiated and remote command injection on a running MCP Server.
Recommendation
- Don't use exec. Use execFile instead, which pins the command and provides the arguments as array elements. - If the user input is not a command-line flag, use the -- notation to terminate command and command-line flag, and indicate that the text after the -- double dash notation is benign value.
References and Prior work
1. Exploiting MCP Servers Vulnerable to Command Injection 2. Liran's Node.js Secure Coding: Defending Against Command Injection Vulnerabilities
Credit
Disclosed by Liran Tal
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-53818?
CVE-2025-53818 is considered a high severity command injection vulnerability.
How do I fix CVE-2025-53818?
To fix CVE-2025-53818, upgrade the GitHub MCP Server to a version beyond 0.4.0.
Which versions are affected by CVE-2025-53818?
CVE-2025-53818 affects GitHub MCP Server versions 0.3.0 and 0.4.0.
What types of attacks can CVE-2025-53818 facilitate?
CVE-2025-53818 can facilitate command injection attacks that may allow an attacker to execute arbitrary commands on the server.
Where can I find more details about CVE-2025-53818?
Detailed information about CVE-2025-53818 can be found in the security advisories provided by GitHub.