Quick answers
- Is CVE-2026-30625 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30625 being exploited in the wild.
- How severe is CVE-2026-30625?
- Critical severity, with a CVSS score of 9.8, published 15 April 2026.
- Which products and versions are affected?
- upsonic (PyPI) < 0.72.0, ECOSYSTEM:introduced=0,fixed=0.72.0.
- Is there a fix for CVE-2026-30625?
- Yes. upsonic (PyPI): upgrade to 0.72.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-30625 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-30625?
- Check whether you run upsonic (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- upsonic (PyPI): upgrade to 0.72.0 or later
pip install "upsonic>=0.72.0"
Technical details
Upsonic 0.71.6 is vulnerable to command injection (CWE-77) within its MCP server/task creation functionality. While the application implements an allowlist for commands, it fails to properly sanitize arguments for permitted binaries such as 'npm' and 'npx'. These binaries support flags that allow for the execution of arbitrary OS commands. A remote attacker can define a crafted MCP task with malicious arguments to achieve remote code execution with the privileges of the Upsonic process. The vulnerability is addressed in version 0.72.0, which includes warnings regarding Stdio server command execution.
Affected products
- Upsonic upsonic < 0.72.0
Identifiers
- CVE-2026-30625
- GHSA-cw73-5f7h-m4gv
- PYSEC-2026-559
Timeline
- 2026-04-15: disclosed
- 2026-04-15: advisory
- 2026-04-15: patched: Version 0.72.0 released