high CVSS 7.8

CVE-2026-34937·Python vulnerability

PraisonAI is a multi-agent teams system. Prior to version 1.5.90, run_python() in praisonai constructs a shell command string by interpolating user-controlled code into python3 -c "<code>" and passing it to subprocess.run(..., shell=True). The escaping logic only handles \ and ", leaving $() and backtick substitutions unescaped, allowing arbitrary OS command execution before Python is invoked. This issue has been patched in version 1.5.90.

Severity
high
Software
Python
Fixed in
1.5.90
Published
2026-04-03

Affected versions

Until: 1.5.90

Fixed in: 1.5.90

How to fix this CVE

Update PraisonAI to version 1.5.90 or later to remediate this command injection vulnerability. The patched version implements proper shell metacharacter escaping in the run_python() function, preventing attackers from injecting arbitrary OS commands through code interpolation. Verify the update has been applied and test your multi-agent workflows to ensure functionality.

sudo dnf upgrade python3-praisonai

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed PraisonAI version: python3 -c "import praisonai; print(praisonai.__version__)"
  2. Verify if run_python() is exposed in your application: grep -r "run_python" /path/to/your/praisonai/code
  3. Search application logs for suspicious shell metacharacters in code execution: grep -E '\$\(|`|\||;|&' /var/log/application.log
  4. Confirm the patch: python3 -c "import praisonai; print('Patched' if praisonai.__version__ >= '1.5.90' else 'Vulnerable')"

FAQ

What is CVE-2026-34937?

This vulnerability exists in PraisonAI's run_python() function, which constructs shell commands by directly interpolating user-supplied code without properly escaping shell metacharacters like $() and backticks. An authenticated attacker can inject arbitrary OS commands that execute before Python, leading to complete system compromise.

Is CVE-2026-34937 being actively exploited?

No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available, though the attack vector is straightforward for anyone with local or authenticated access.

What versions of PraisonAI are affected by CVE-2026-34937?

All versions of PraisonAI prior to 1.5.90 are vulnerable. Version 1.5.90 and later include the security patch.

How do I check if my server is vulnerable to CVE-2026-34937?

Run: python3 -c "import praisonai; print(praisonai.__version__)" and verify the version is 1.5.90 or later. If the version is lower, your system is vulnerable.

Does Defensia detect CVE-2026-34937?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PraisonAI is installed on a monitored server, CVE-2026-34937 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-9135CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 Langflow versions up to 1.9.2 (commit 94981c443d4918517b9e8163d70fc598dc33a32d) contain a code injection vulnerability in the Policies component's ToolGuard integration that bypasses the allow_custom_components=false security control. The vulnerability exists because the validation mechanism only checks the main component source code in node_template["code"]["value"] but fails to validate dynamic CodeInput fields that store generated ToolGuard Python files. Attackers can embed malicious Python code in these unvalidated dynamic fields, which are persisted in Flow.data and later executed server-side when a guarded tool is invoked through the ToolGuard runtime. This allows authenticated users with flow creation privileges to achieve arbitrary Python code execution on the backend despite custom component restrictions. The vulnerability can be escalated through cross-tenant flow manipulation via the agentic MCP update_flow_component_field tool, which accepts attacker-controlled user_id parameters, enabling attackers to inject malicious code into victim users' flows. When combined with publicly accessible flows and specific misconfigurations (AUTO_LOGIN=true, NEW_USER_IS_ACTIVE=true), the attack can be conducted with reduced authentication requirements.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-34937. Free for 1 server.

Get started free