External risk intelligence

Attacker can take control of Upsonic systems by sending malicious tasks

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-30625

An internal attacker with access to the Upsonic management interface can run unauthorized system commands. This allows them to execute malicious code, which could result in full server control and exposure of sensitive data.

3Halo Surface Signal

Remote Code Execution

External exposure likelihood

Halo Surface Signal score for CVE-2026-30625

The vulnerability exists in a management interface for AI and development infrastructure. While typically restricted to internal networks, such web-based interfaces are increasingly deployed in cloud environments, making them plausibly reachable from the internet depending on specific configuration choices, though they are not public-facing by design.

Horizon Alert

Summary of the vulnerability and why it matters

This issue in Upsonic allows for remote code execution, meaning an attacker could potentially run commands on your system. It's a significant concern because it bypasses existing security checks for certain commands, enabling unauthorized control with the privileges of the Upsonic process.

  • Attackers can execute arbitrary code.
  • It impacts the integrity of your systems.
  • This affects users with existing access.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by crafting malicious MCP tasks within Upsonic, targeting the command and arguments functionality. Even though some commands are allowlisted, specific arguments for commands like `npm` or `npx` can be manipulated to execute arbitrary OS commands. This could lead to remote code execution with the privileges of the Upsonic process.

  • No authentication required.
  • Target MCP server task creation.
  • Use `npm` or `npx` with malicious arguments.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in Upsonic's MCP server allows for remote code execution due to improperly handled command arguments, even with an allowlist. Attackers are likely to target this because it offers unauthenticated remote code execution, a highly desirable outcome for initial compromise or lateral movement. The ability to leverage existing commands like `npm` or `npx` for unintended purposes makes exploitation more straightforward.

  • Unauthenticated remote code execution.
  • Leverages common development tools.
  • Disclosure in April 2026.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams should prioritize identifying and isolating Upsonic instances using versions prior to 0.72.0 that expose the MCP server. Given the critical severity and potential for unauthenticated remote code execution, any exposed Upsonic instances should be immediately taken offline or network-isolated until patched. Monitor for signs of exploitation, such as unexpected process execution or network connections originating from the Upsonic server.

  • Apply Upsonic version 0.72.0 or later.
  • Isolate affected servers from network access.
  • Audit logs for suspicious command executions.

Frequently asked questions

What is Upsonic and what is it used for?

Upsonic is a system that allows users to define tasks, including the creation of MCP (likely a job or task management protocol) tasks with specified commands and arguments. It is used in managing development and AI infrastructure, enabling automated execution of commands and processes.

What weakness does CVE-2026-30625 represent?

CVE-2026-30625 is a remote code execution vulnerability, specifically identified as CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'). This means that special characters or command structures intended for one purpose can be misused to execute unintended commands on the system.

How can an attacker exploit this vulnerability?

An attacker can exploit this by crafting malicious MCP tasks. Although Upsonic has an allowlist for commands, certain allowed commands like `npm` or `npx` can accept argument flags that enable the execution of arbitrary operating system commands, leading to a compromise.

Who should be concerned about this threat?

Organizations using Upsonic versions prior to 0.72.0 should be concerned. Halo Surface Signal indicates this vulnerability has a 'Possible' exposure, suggesting it could be reachable from the internet depending on how Upsonic is configured, even if not designed as a public-facing service.

What is the first step to address this vulnerability?

The immediate first step is to upgrade Upsonic to version 0.72.0 or later. If upgrading is not immediately possible, affected servers should be isolated from the network to prevent potential exploitation until a patch can be applied.

References