How severe is CVE-2026-25546?

CVE-2026-25546 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-25546?

CVE-2026-25546 affects the following packages: @coding-solo/godot-mcp (npm). Ecosystems affected: npm.

How do I fix CVE-2026-25546?

Update @coding-solo/godot-mcp to 0.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25546 is resolved across your whole dependency graph.

How do I detect CVE-2026-25546 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @coding-solo/godot-mcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-25546 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2026-25546 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-25546 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-25546?

CVE-2026-25546 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-25546?

CVE-2026-25546 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-25546 published, and has it been updated?

CVE-2026-25546 was published on February 4, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

CVE-2026-25546 — @coding-solo/godot-mcp

HIGHFix: Coding-Solo/godot-mcp@21c785d

CVE-2026-25546 is a high-severity (CVSS 7.8) OS Command Injection vulnerability in @coding-solo/godot-mcp. A fix is available for @coding-solo/godot-mcp — see the affected versions and patch details below.

Godot MCP is vulnerable to Command Injection via unsanitized projectPath

Also known asGHSA-8jx2-rhfh-q928

Published

Feb 4, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25546.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk+0.06%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@coding-solo/godot-mcpnpm

3Kdownloads / week

Description

Impact

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.

Patches

Fixed in version 0.1.1 by switching from exec() to execFile(), which does not invoke a shell.

Workarounds

None. Users should upgrade immediately.

Resources

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@coding-solo/godot-mcp`	all versions	0.1.1`npm install @coding-solo/godot-mcp@0.1.1`

Affected Products

1 product · 1 configurations

Application

godot mcpcoding-solo

< 0.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @coding-solo/godot-mcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @coding-solo/godot-mcp to 0.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25546 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact 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. ### Patches Fixed in version 0.1.1 by switching from `exec()` to `execFile()`, which does not invoke a shell.