https://feed.craftedsignal.io/products/code-mcp/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 05 May 2026 05:16:00 +0000https://feed.craftedsignal.io/briefs/2026-05-code-mcp-command-injection/Tue, 05 May 2026 05:16:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-code-mcp-command-injection/A command injection vulnerability (CVE-2026-7812) exists in the git_operation function of 54yyyu code-mcp's MCP Tool, allowing remote attackers to execute arbitrary commands by manipulating the operation argument.A command injection vulnerability has been identified in 54yyyu’s code-mcp, specifically affecting versions up to commit 4cfc4643541a110c906d93635b391bf7e357f4a8. The vulnerability resides in the git_operation function within src/code_mcp/server.py of the MCP Tool component. This flaw allows a remote attacker to inject and execute arbitrary commands by manipulating the operation argument. The exploit is publicly available, increasing the risk of exploitation. 54yyyu employs a continuous delivery model with rolling releases, making it difficult to pinpoint specific vulnerable versions and updated releases. The project maintainers were notified of the vulnerability through an issue report but have not yet provided a response or patch.

Attack Chain

1. The attacker identifies a publicly accessible instance of 54yyyu code-mcp running a vulnerable version (<= 4cfc4643541a110c906d93635b391bf7e357f4a8).
2. The attacker crafts a malicious HTTP request targeting the git_operation function in src/code_mcp/server.py.
3. The malicious request includes a crafted operation argument containing shell commands.
4. The git_operation function, without proper sanitization, passes the attacker-controlled operation argument to a system call.
5. The system executes the injected commands, potentially allowing the attacker to execute arbitrary code on the server.
6. The attacker gains initial access and may attempt to escalate privileges.
7. The attacker moves laterally within the network, compromising other systems and data.
8. The attacker achieves their final objective, which could include data exfiltration, ransomware deployment, or system disruption.

Impact

Successful exploitation of this vulnerability allows a remote attacker to execute arbitrary commands on the affected system. Due to the lack of specific versioning information and response from the vendor, the exact number of vulnerable installations is unknown. This vulnerability could lead to complete system compromise, data breaches, and potential disruption of services, impacting any organization using the affected 54yyyu code-mcp software.

Recommendation

• Inspect web server logs for suspicious POST requests to the git_operation endpoint in src/code_mcp/server.py containing shell command injection attempts, and deploy the Detect Suspicious Git Operation Requests Sigma rule.
• Monitor process creation events for unusual processes spawned by the code-mcp application or related processes, using the Detect Suspicious Processes Spawned by Code-MCP Sigma rule.
• Since no patch is available, consider implementing input validation and sanitization on the operation argument within the git_operation function or consider isolating the affected service until a patch is released.

]]>highadvisorycommand-injectionweb-applicationcve-2026-7812https://feed.craftedsignal.io/briefs/2024-01-03-code-mcp-path-traversal/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-03-code-mcp-path-traversal/A path traversal vulnerability exists in the is_safe_path function of the MCP File Handler component in 54yyyu code-mcp, allowing remote attackers to access sensitive files.A path traversal vulnerability, identified as CVE-2026-7811, has been discovered in 54yyyu code-mcp, affecting versions up to commit 4cfc4643541a110c906d93635b391bf7e357f4a8. This flaw resides within the is_safe_path function in src/code_mcp/server.py, a part of the MCP File Handler component. The vulnerability enables remote attackers to bypass security restrictions and potentially access unauthorized files and directories on the server. The exploit is publicly known. The vendor employs rolling releases, making specific version details unavailable, and has not yet responded to the initial vulnerability report. This lack of response and public exploit availability poses a significant risk to systems running the affected code-mcp versions.

Attack Chain

1. The attacker identifies a vulnerable instance of 54yyyu code-mcp running a version with the affected is_safe_path function.
2. The attacker crafts a malicious HTTP request targeting the MCP File Handler, specifically designed to invoke the vulnerable is_safe_path function.
3. The crafted request includes a path containing directory traversal sequences (e.g., ../) intended to bypass the path validation logic.
4. The is_safe_path function fails to properly sanitize the input path, allowing the traversal sequences to be processed.
5. The application attempts to access a file or directory outside of the intended base directory based on the attacker-controlled path.
6. The server reads the contents of the file or directory and includes it in the HTTP response.
7. The attacker receives the sensitive information, such as configuration files or source code.
8. The attacker can then use this information to further compromise the system or network.

Impact

Successful exploitation of this path traversal vulnerability can allow attackers to read sensitive files from the server hosting the 54yyyu code-mcp application. This may include configuration files, source code, or other data that could aid in further attacks, such as privilege escalation or lateral movement. Since the exploit is publicly available, unpatched systems are at immediate risk of compromise. The number of affected installations and the specific sectors impacted are currently unknown, but the potential for data breaches and system compromise is significant.

Recommendation

• Deploy the Sigma rule Detect Code-mcp Path Traversal Attempt to identify requests containing suspicious path traversal sequences in the cs-uri-query field of web server logs.
• Enable web server logging to capture HTTP requests and responses, which is required for the Sigma rule to function correctly (logsource: webserver).
• Since specific patched versions are unavailable due to the rolling release model, monitor the vendor’s code repository for updates to the is_safe_path function in src/code_mcp/server.py and deploy the updated code as soon as it becomes available.
• Implement a web application firewall (WAF) rule to block requests containing path traversal sequences like ../ in URL parameters to mitigate the risk proactively.

]]>highadvisorypath-traversalweb-applicationCVE-2026-7811