External risk intelligence

Command Injection in terminal-controller-mcp 0.1.7

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2025-61492

The product, terminal-controller-mcp, is an integration component for Model Context Protocol (MCP). While MCP servers can be exposed as network services to provide tools to LLMs, they are frequently deployed as local or internal developer-focused utilities. Public internet exposure is possible depending on the deployment architecture, but it is not a defining characteristic of this type of tool.

Command Injection

Gongrzhe Terminal Controller Mcp

0.1.7

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A command injection vulnerability has been identified in the terminal-controller-mcp software, potentially allowing unauthorized individuals to execute arbitrary commands on affected systems. This type of vulnerability is critical due to its ability to grant full control over a system if exploited. The primary concern is to confirm if this specific software is in use and, if so, to assess any potential exposure.

Allows remote execution of commands.
Critical for potential system compromise.
Confirm use and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending specially crafted input to the affected component, which does not require any authentication or user interaction. The vulnerability lies within the `execute_command` function, allowing for arbitrary command execution on the target system. This could lead to a complete compromise of the affected system.

No authentication or user interaction needed.
Triggered by crafted input to a function.
Allows arbitrary command execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker could execute arbitrary commands by sending crafted input to the `execute_command` function of terminal-controller-mcp. This could impact the integrity and availability of the system.

Arbitrary command execution on the system.
Network-accessible input can trigger command execution.
System compromise and unauthorized data access.

Operational Fix

Recommended remediation, mitigation, and detection steps

The terminal-controller-mcp product is an integration component for Model Context Protocol (MCP). System owners and security teams should first identify all instances of this software within their environment, determine their accessibility from external networks, and confirm business criticality. Subsequently, they should engage the accountable application or platform owner to prioritize and plan remediation efforts based on the assessed risk.

App or platform owners should triage.
Verify external network exposure first.
Plan remediation or risk reduction.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is terminal-controller-mcp?

terminal-controller-mcp is a software component used to integrate tools with the Model Context Protocol (MCP). It is typically used as a utility by developers to allow LLMs to interact with terminal environments. Because it functions as an MCP server, it acts as a bridge that provides specific command-line capabilities to the AI models connected to it.

What does CWE-77 mean for CVE-2025-61492?

CVE-2025-61492 involves CWE-77, which is the weakness class for improper neutralization of special elements used in a command. In plain terms, this means the software incorrectly handles user-supplied data, allowing an attacker to inject and execute their own system commands. Because this occurs in the execute_command function, the software effectively runs malicious instructions as if they were intended legitimate tasks.

How is this command injection triggered?

An attacker triggers this vulnerability by sending specially crafted input to the affected terminal-controller-mcp component. Importantly, this process does not require any authentication, permissions, or manual user interaction to execute. The flaw exists in how the code processes input, meaning simple delivery of the malicious data is enough to initiate the command execution.

Is my system at risk from CVE-2025-61492?

Risk depends on how you have deployed the software. According to Halo Surface Signal, terminal-controller-mcp is often used as a local or internal developer utility, which typically limits access. However, because MCP servers can be configured as network services, you should verify if your instance is reachable from the public internet, as that significantly increases the potential for unauthorized remote access.

How should I respond to this vulnerability?

Your first step is to inventory your environment to locate all instances of terminal-controller-mcp. Once found, verify their network accessibility to see if they are exposed externally or restricted to internal use. Work with the relevant application or platform owners to assess the business risk of these instances and prioritize remediation efforts, such as updating the software or isolating it from untrusted networks.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.