dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-30625

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Upsonic 0.71.6 MCP server allows users to define tasks with arbitrary command and args values. While an allowlist restricts allowed commands, whitelisted commands like npm and npx accept argument flags that enable execution of arbitrary OS commands, leading to RCE with the privileges of the Upsonic process.

MitigationUpgrade to version 0.72.0 or later which includes warnings about Stdio server risks, and implement strict command validation to prevent injection through whitelisted utilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Upsonic installation and version
    Run 'pip show upsonic' or check your package manager for the installed version of the upsonic package
    Affected if The installed version is 0.71.6 or any version earlier than 0.72.0
  2. Locate the Upsonic configuration file
    Look for a config file named upsonic.json, upsonic.yaml, or a .upsonic directory in the user's home or project root
    Affected if The configuration file exists and the MCP server component is enabled
  3. Verify MCP server task feature is enabled
    Inspect the configuration file for MCP server settings, specifically looking for 'server' or 'mcp' sections with task-related capabilities
    Affected if The MCP server is configured with task execution capabilities present
  4. Check for npm/npx command definitions in tasks
    Search configuration files for task definitions that reference 'npm' or 'npx' commands with user-controlled arguments
    Affected if Tasks using whitelisted commands (npm, npx) with arbitrary argument flags are defined or can be defined

You are affected if Upsonic version 0.71.6 or earlier is installed AND the MCP server with task functionality is enabled, allowing arbitrary command arguments through whitelisted utilities like npm or npx.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.72.0 or later which includes warnings about Stdio server risks, and implement strict command validation to prevent injection through whitelisted utilities.

Recommended fix Moderate confidence

0.72.0 or later

  1. 1. Identify the current Upsonic version installed in your environment (e.g., check requirements.txt, pyproject.toml, or pip list)
  2. 2. Upgrade to Upsonic version 0.72.0 or later by running: pip install --upgrade upsonic>=0.72.0
  3. 3. After upgrading, review the warning about Stdio servers being able to execute commands directly on the machine
  4. 4. Audit existing MCP task configurations to ensure no malicious tasks were created
  5. 5. Implement additional input validation on MCP task command and args if the application is exposed to untrusted users
Caveat The upgrade adds a warning about Stdio server command execution; no API breaking changes mentioned

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30625 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30625 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data