7.8

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-25546

CVE-2026-25546: Godot MCP is vulnerable to Command Injection via unsanitized projectPath

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-25546

CVE-2026-25546:

7.8

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
@coding-solo/godot-mcp	npm	< 0.1.1	0.1.1

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability exists because the godot-mcp package used the child_process.exec function, which spawns a shell, to execute commands. The primary vulnerable function is GodotServer.executeOperation, which constructs a command string that includes a user-controlled projectPath. An attacker could provide a malicious projectPath containing shell metacharacters (e.g., $(reboot)) to execute arbitrary commands on the server where godot-mcp is running. The patch addresses this by replacing all instances of exec with execFile. The execFile function does not use a shell and accepts arguments as an array, which prevents command injection. While the advisory focuses on executeOperation, the patch also fixed several other functions that were using the same vulnerable pattern with exec, mitigating a broader potential risk.

Vulnerable functions

GodotServer.executeOperation

src/index.ts

The `executeOperation` function was vulnerable to command injection because it used `exec` to run a command constructed with user-provided `projectPath`. An attacker could inject shell metacharacters into `projectPath` to execute arbitrary commands. The patch replaced `exec` with `execFile`, which does not spawn a shell and passes arguments safely.

GodotServer.validateGodotPath

src/index.ts

The `validateGodotPath` function used `exec` to run a command with a `path` variable. While not the primary vulnerability, this pattern is dangerous if the path could be influenced by an attacker. The patch proactively replaced `exec` with the safer `execFile`.

GodotServer.getGodotVersion

src/index.ts

The `getGodotVersion` function used `exec` to get the Godot version. This was part of a larger pattern of using the unsafe `exec` function throughout the class. The patch replaced it with `execFile` to prevent potential command injection vulnerabilities.

GodotServer.getContext

src/index.ts

The `getContext` function used `exec` to get the Godot version. This was part of a larger pattern of using the unsafe `exec` function throughout the class. The patch replaced it with `execFile` to prevent potential command injection vulnerabilities.

GodotServer.getSceneTree

src/index.ts

The `getSceneTree` function used `exec` to get the Godot version. This was part of a larger pattern of using the unsafe `exec` function throughout the class. The patch replaced it with `execFile` to prevent potential command injection vulnerabilities.

GodotServer.getScriptInfo

src/index.ts

The `getScriptInfo` function used `exec` to get the Godot version. This was part of a larger pattern of using the unsafe `exec` function throughout the class. The patch replaced it with `execFile` to prevent potential command injection vulnerabilities.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.