CVE-2026-0756

Multiple · Multiple Products (specifically the github-kanban-mcp-server component)

A critical remote code execution vulnerability, identified as CVE-2026-0756, has been discovered in github-kanban-mcp-server.

Executive summary

A critical remote code execution vulnerability, identified as CVE-2026-0756, has been discovered in github-kanban-mcp-server. This flaw allows an unauthenticated remote attacker to execute arbitrary commands on the server, potentially leading to a complete system compromise. Due to the lack of required authentication and the high severity score, this vulnerability poses a significant and immediate risk to affected organizations.

Vulnerability

The vulnerability is a command injection flaw within the github-kanban-mcp-server. The specific weakness exists in how the application processes the create_issue parameter. An attacker can send a specially crafted request containing malicious commands within this parameter. The server fails to properly sanitize this user-supplied input before using it to execute a system call, allowing the injected commands to be executed on the underlying operating system with the privileges of the service account.

Business impact

This vulnerability is rated as critical severity with a CVSS score of 9.8. Successful exploitation could lead to a complete compromise of the affected server. Potential consequences include theft or modification of sensitive data, deployment of ransomware, service disruption, and using the compromised server as a pivot point for further attacks within the internal network. The business risks include significant data breaches, reputational damage, financial loss, and potential regulatory fines.

Remediation

Immediate Action: Organizations must prioritize the deployment of vendor-supplied patches. Update all affected instances of products containing the github-kanban-mcp-server component to the latest secure version immediately. After patching, review server access logs and application logs for any signs of compromise or exploitation attempts that may have occurred before the patch was applied.

Proactive Monitoring: Implement enhanced monitoring on affected systems. Security teams should look for unusual process execution initiated by the service account, unexpected outbound network connections from the server, and review web server access logs for requests to the vulnerable endpoint containing shell metacharacters (e.g., |, &, ;, $()) within the create_issue parameter.

Compensating Controls: If immediate patching is not feasible, consider implementing the following controls:

  • Deploy a Web Application Firewall (WAF) with rules specifically designed to block command injection attempts targeting the create_issue parameter.
  • Restrict network access to the affected application, allowing connections only from trusted IP addresses.
  • If possible, run the service in a sandboxed or containerized environment with minimal privileges to limit the impact of a potential compromise.

Exploitation status

Public Exploit Available: False

Analyst recommendation

Given the critical CVSS score of 9.8 and the fact that no authentication is required for exploitation, this vulnerability represents a severe and urgent threat. We strongly recommend that organizations identify all affected assets and apply the vendor-provided patches with the highest priority. Although this CVE is not currently on the CISA KEV list, its characteristics make it a prime candidate for future inclusion and active exploitation. Treat this vulnerability as an active threat and remediate it without delay.