Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25546: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in Coding-Solo godot-mcp

0
High
VulnerabilityCVE-2026-25546cvecve-2026-25546cwe-78
Published: Wed Feb 04 2026 (02/04/2026, 21:48:53 UTC)
Source: CVE Database V5
Vendor/Project: Coding-Solo
Product: godot-mcp

Description

Godot MCP is a Model Context Protocol (MCP) server for interacting with the Godot game engine. Prior to version 0.1.1, a command injection vulnerability in godot-mcp allows remote code execution. The executeOperation function passed user-controlled input (e.g., projectPath) directly to exec(), which spawns a shell. An attacker could inject shell metacharacters like $(command) or &calc to execute arbitrary commands with the privileges of the MCP server process. This affects any tool that accepts projectPath, including create_scene, add_node, load_sprite, and others. This issue has been patched in version 0.1.1.

AI-Powered Analysis

AILast updated: 02/04/2026, 22:14:43 UTC

Technical Analysis

CVE-2026-25546 is an OS command injection vulnerability classified under CWE-78 affecting the godot-mcp server, a Model Context Protocol server used to interact with the Godot game engine. The root cause is the executeOperation function passing user-controlled input, specifically the projectPath parameter, directly to the exec() system call without proper sanitization or neutralization of shell metacharacters. This allows attackers to inject arbitrary shell commands using constructs like $(command) or &calc, which the shell interprets and executes with the privileges of the MCP server process. The vulnerability affects all operations that accept projectPath, including create_scene, add_node, and load_sprite, making it broadly exploitable within the godot-mcp functionality. The vulnerability requires user interaction but no authentication, increasing the attack surface especially in environments where godot-mcp is exposed to untrusted users or network segments. The vulnerability was publicly disclosed on February 4, 2026, with a CVSS v3.1 score of 7.8, indicating high severity. Although no known exploits are currently reported in the wild, the ease of exploitation and potential impact on confidentiality, integrity, and availability make it critical to address. The vendor has released version 0.1.1 which patches this issue by properly sanitizing inputs before passing them to exec().

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially for those involved in game development, digital media, or any sector leveraging the Godot engine and godot-mcp for automation or integration. Successful exploitation could lead to remote code execution, allowing attackers to compromise the confidentiality of sensitive project data, alter or corrupt game assets or code (integrity), and disrupt development workflows or production environments (availability). This could result in intellectual property theft, sabotage of development pipelines, or broader network compromise if the MCP server privileges extend beyond isolated environments. Given the high CVSS score and the nature of the vulnerability, organizations face a risk of lateral movement and persistent compromise if the MCP server is accessible from less trusted networks or exposed to external users. The absence of required authentication and the reliance on user interaction mean phishing or social engineering could facilitate exploitation. The impact is amplified in environments where godot-mcp is integrated into continuous integration/continuous deployment (CI/CD) pipelines or automated build systems.

Mitigation Recommendations

European organizations should immediately upgrade all godot-mcp instances to version 0.1.1 or later to apply the official patch that neutralizes shell metacharacters in user inputs. Until patching is possible, restrict network access to the MCP server to trusted internal networks only, employing strict firewall rules and network segmentation to minimize exposure. Implement input validation and sanitization at the application layer to reject or escape shell metacharacters in parameters like projectPath. Employ application-level logging and monitoring to detect anomalous command execution patterns or unexpected process spawning. Use least privilege principles for the MCP server process, ensuring it runs with minimal permissions to limit the impact of potential exploitation. Educate developers and users about the risks of interacting with untrusted inputs and the importance of applying updates promptly. Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect and block suspicious command injection attempts. Finally, review and audit CI/CD pipelines and integration points for exposure to this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-02T19:59:47.375Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6983c169f9fa50a62faf7b03

Added to database: 2/4/2026, 10:00:09 PM

Last enriched: 2/4/2026, 10:14:43 PM

Last updated: 2/6/2026, 6:13:49 PM

Views: 34

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats