CVE-2026-30625: Upsonic: remote code execution vulnerability in its MCP server/task creation functionality
Upsonic 0.71.6 lets users define MCP tasks with arbitrary `command` and `args`. The allowlist includes `npm` and `npx`, whose argument flags can run any OS command, so a crafted task executes code with the privileges of the Upsonic process. The fixed version is 0.72.0, which adds a warning about Stdio servers.
Published Apr 15, 2026 · Updated Apr 16, 2026 · Analysis Oct 30, 2026
What an attacker can do
Upsonic's MCP server and task creation feature accepts a command and args pair for a Stdio MCP server. An allowlist limits which commands may be used. But npm and npx are on it, and both accept flags that run arbitrary programs. A task that uses an allowed command with such flags bypasses the intent of the list.
The CVSS 3.1 vector (9.8) says the attacker is remote and needs no privileges or user interaction. In practice that applies to any deployment where untrusted users or an exposed endpoint can create MCP tasks. They get code execution as the Upsonic process, which means its environment variables, API keys, files and network position.
The flaw lies in how an agent platform launches tool servers as local processes. The 0.72.0 note in the description says Upsonic added a warning that Stdio servers can execute commands directly on the machine. That wording suggests the project treats command launching as a trust decision for the operator. The sources do not describe a tighter allowlist.
Who is affected
pip package upsonic before 0.72.0, with 0.71.6 named as affected. Deployments that let users or integrations define MCP tasks are exposed. Check:
pip show upsonicupsonic
- Ecosystem
- PyPI
- Affected
- < 0.72.0
- Fixed in
- 0.72.0
- Check
pip show upsonic
How to fix it
Upgrade to upsonic 0.72.0:
pip install -U "upsonic>=0.72.0"Per the description, 0.72.0 adds a warning about Stdio servers executing commands on the machine. It does not say the allowlist was rewritten. Treat the warning as a sign that you must restrict who can define MCP tasks, and run Upsonic with minimal privileges and no unneeded secrets.
How to tell if you were hit
Review stored or submitted MCP task definitions for a command of npm or npx with unusual args, such as flags that execute scripts or fetch remote packages. Check process trees under the Upsonic process for unexpected children, and outbound connections from them. Review who created MCP tasks and when.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Upsonic 0.71.6 contains a remote code execution vulnerability in its MCP server/task creation functionality. The application allows users to define MCP tasks with arbitrary command and args values. Although an allowlist exists, certain allowed commands (npm, npx) accept argument flags that enable execution of arbitrary OS commands. Maliciously crafted MCP tasks may lead to remote code execution with the privileges of the Upsonic process. In version 0.72.0 Upsonic added a warning about using Stdio servers being able to execute commands directly on the machine.
Questions
- Is Upsonic 0.71.6 affected by CVE-2026-30625?
Yes. The description names 0.71.6, and the package data lists versions below 0.72.0 as vulnerable.
- Why does an allowlist not stop it?
The allowed commands
npmandnpxtake arguments that run arbitrary OS commands, so allowing the binary also allows what it can launch.- Which version fixes it?
0.72.0. It adds a warning about Stdio servers running commands directly on the machine.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More Other MCP servers and tools vulnerabilities
All Other MCP servers and tools entriesCVE-2026-102943
Dagu MCP DAG specification read bypasses path containment and workspace isolation
medium6.5Nov 10, 2026CVE-2026-102610
fast-agent: `fast-agent serve` binds HTTP to 0.0.0.0 with no authentication by default; with --shell this is unauthenticated remote command execution
medium6.4Nov 9, 2026CVE-2026-63655
tsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS
high7.5Nov 9, 2026CVE-2026-76892
tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP process
high8.7Nov 9, 2026CVE-2026-76893
tsParticles: A single anonymous MCP session can monopolize HTTP mode and deny new clients
medium6.9Nov 9, 2026CVE-2026-77604
Code Graph RAG: MCP paginated read_file path traversal / arbitrary file read
high7.5Nov 9, 2026
