# CVE-2025-61492: terminal-controller-mcp vulnerable to Command Injection

> Attackers can execute arbitrary commands via crafted input in the terminal-controller-mcp library, requiring an upgrade to mitigate.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-h4rf-624j-gj33, PYSEC-2026-551

## What is CVE-2025-61492?

CVE-2025-61492 is a critical command injection vulnerability in n/a, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A command injection vulnerability in the execute_command function of terminal-controller-mcp 0.1.7 allows attackers to execute arbitrary commands via a crafted input.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-61492?

3 open source packages ship an affected version, including terminal-controller. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `terminal-controller` | PyPI | All versions to 0.1.7 | None |
| `terminal-controller` | PyPI | All versions to 0.1.7 | None |
| `terminal-controller` | PyPI | All versions to 0.1.7 | None |

Products: Gongrzhe Terminal-Controller-Mcp.

## How do I fix CVE-2025-61492?

No fix has been published for CVE-2025-61492 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-61492 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61492 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61492 and fix it if it is affected.

What it is: CVE-2025-61492 is a critical command injection vulnerability in n/a, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61492 exists.

Affected packages and fixed versions:
- terminal-controller (PyPI): affected all versions up to 0.1.7; no fix listed
- terminal-controller (PyPI): affected all versions up to 0.1.7; no fix listed
- terminal-controller (PyPI): affected all versions up to 0.1.7; no fix listed

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-2025-61492/ (Markdown: https://insights.sbomify.com/CVE-2025-61492/index.md)
```

## Sources

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

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