Quick answers
- Is CVE-2026-34935 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34935 being exploited in the wild.
- How severe is CVE-2026-34935?
- Critical severity, with a CVSS score of 9.8, published 3 April 2026.
- Which products and versions are affected?
- praisonai (PyPI) ECOSYSTEM:introduced=4.5.15,fixed=4.5.69.
- Is there a fix for CVE-2026-34935?
- Yes. praisonai (PyPI): upgrade to 4.5.69 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34935 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-34935?
- Check whether you run Praisonai or praisonai (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
- praisonai (PyPI): upgrade to 4.5.69 or later
pip install "praisonai>=4.5.69"
Technical details
An OS command injection vulnerability exists in PraisonAI's MCPHandler component. The root cause is the lack of sanitization or validation of the `--mcp` command-line argument, which is passed through `shlex.split()` and eventually reaches the `anyio.open_process()` sink. An attacker can exploit this by supplying shell commands (e.g., using `bash -c`) within the `--mcp` argument. This allows for arbitrary code execution with the privileges of the user running the PraisonAI process. The vulnerability is reachable over the network if the CLI arguments are influenced by untrusted input. The issue is resolved in version 4.5.69 by implementing a command allowlist (restricting execution to npx, uvx, node, and python).
Affected products
- MervinPraison PraisonAI >= 4.5.15, < 4.5.69
Identifiers
- CVE-2026-34935
- GHSA-9gm9-c8mq-vq7m
- PYSEC-2026-471
Timeline
- 2026-03-31: advisory: Original GitHub Security Advisory published
- 2026-04-03: disclosed: CVE published to NVD
- 2026-04-03: patched: Fix released in version 4.5.69