# CVE-2026-34937: PraisonAI: Shell Injection in run_python() via Unescaped $() Substitution

> Attackers can execute arbitrary OS commands via shell injection in PraisonAI's run_python function due to insufficient escaping of user-controlled code.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-w37c-qqfp-c67f, PYSEC-2026-2954

## What is CVE-2026-34937?

CVE-2026-34937 is a high-severity command injection vulnerability in MervinPraison PraisonAI, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-34937?

3 open source packages ship an affected version, including praisonaiagents. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonaiagents` | PyPI | All versions | 1.5.90 |
| `praisonaiagents` | PyPI | All versions | 1.5.90 |
| `praisonaiagents` | PyPI | All versions | 1.5.90 |

Products: Praison Praisonaiagents.

## How do I fix CVE-2026-34937?

Upgrade praisonaiagents to 1.5.90 or later.

## Is CVE-2026-34937 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34937 exists.

## Other vulnerabilities in MervinPraison PraisonAI

- [CVE-2026-34938](https://insights.sbomify.com/CVE-2026-34938/): PraisonAI: Python Sandbox Escape via str Subclass startswith() Override in execute_code (critical 10.0)
- [CVE-2026-40111](https://insights.sbomify.com/CVE-2026-40111/): PraisonAIAgents has an OS Command Injection via shell=True in Memory Hooks Executor (memory/hooks.py) (critical 9.3)
- [CVE-2026-34954](https://insights.sbomify.com/CVE-2026-34954/): PraisonAI: SSRF in FileTools.download_file() via Unvalidated URL (high 8.6)
- [CVE-2026-44335](https://insights.sbomify.com/CVE-2026-44335/): SSRF bypass in PraisonAI (high 7.7)
- [CVE-2026-40150](https://insights.sbomify.com/CVE-2026-40150/): PraisonAIAgents has SSRF and Local File Read via Unvalidated URLs in web_crawl Tool (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34937 and fix it if it is affected.

What it is: CVE-2026-34937 is a high-severity command injection vulnerability in MervinPraison PraisonAI, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34937 exists.

Affected packages and fixed versions:
- praisonaiagents (PyPI): affected all versions; fixed in 1.5.90
- praisonaiagents (PyPI): affected all versions; fixed in 1.5.90
- praisonaiagents (PyPI): affected all versions; fixed in 1.5.90

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34937/ (Markdown: https://insights.sbomify.com/CVE-2026-34937/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34937
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34937
- OSV: https://osv.dev/vulnerability/CVE-2026-34937

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34937/
Summaries are generated and may contain mistakes; the official description above is the record.