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


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Feb 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-8jx2-rhfh-q928

## What is CVE-2026-25546?

CVE-2026-25546 is a high-severity vulnerability in Coding-Solo godot-mcp, published on 4 Feb 2026. 

### Official 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-25546?

2 open source packages ship an affected version, including @coding-solo/godot-mcp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@coding-solo/godot-mcp` | npm | All versions | 0.1.1 |
| `@coding-solo/godot-mcp` | npm | All versions | 0.1.1 |

Products: Coding-Solo Godot Mcp.

## How do I fix CVE-2026-25546?

Upgrade @coding-solo/godot-mcp to 0.1.1 or later.

## Is CVE-2026-25546 being exploited?

There is no known exploitation of CVE-2026-25546 in the wild and no public exploit code.

Public exploit code:

- https://github.com/mbanyamer/CVE-2026-25546-godot-mcp-0.1.1-OS-Command-Injection (github_poc): https://github.com/mbanyamer/CVE-2026-25546-godot-mcp-0.1.1-OS-Command-Injection

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25546 and fix it if it is affected.

What it is: CVE-2026-25546 is a high-severity vulnerability in Coding-Solo godot-mcp, published on 4 Feb 2026. 
Exploitation: There is no known exploitation of CVE-2026-25546 in the wild and no public exploit code.

Affected packages and fixed versions:
- @coding-solo/godot-mcp (npm): affected all versions; fixed in 0.1.1
- @coding-solo/godot-mcp (npm): affected all versions; fixed in 0.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25546/ (Markdown: https://insights.sbomify.com/CVE-2026-25546/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25546
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25546
- OSV: https://osv.dev/vulnerability/CVE-2026-25546

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25546/
Summaries are generated and may contain mistakes; the official description above is the record.
