# CVE-2026-47392: PraisonAI vulnerable to sandbox escape via `print.__self__` builtins module leak in `execute_code` (subprocess mode)

> Attackers can bypass the Python sandbox in PraisonAI to execute arbitrary OS commands on the host by leaking builtins via print.__self__.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-4mr5-g6f9-cfrh, PYSEC-2026-463, PYSEC-2026-483

## What is CVE-2026-47392?

CVE-2026-47392 is a critical code injection vulnerability in MervinPraison < 1.6.40, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PraisonAI is a multi-agent teams system. Prior to version 4.6.40 of PraisonAI, corresponding to version 1.6.40 of praisonaiagents, `execute_code()` in `praisonaiagents/tools/python_tools.py` (v1.6.37, subprocess sandbox mode) can be fully bypassed using `print.__self__` to retrieve the real Python `builtins` module, from which `__import__` can be extracted via `vars()` and runtime string construction. This achieves arbitrary OS command execution on the host, completely defeating the sandbox. This is a novel bypass that survives all patches for CVE-2026-39888 (frame traversal), CVE-2026-34938 (str subclass), and CVE-2026-40158 (`type.__getattribute__` trampoline). PraisonAI version 4.6.40 and praisonaiagents version 1.6.40 contain an updated fix.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-184 (Incomplete List of Disallowed Inputs)

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

6 open source packages ship an affected version, including praisonaiagents, PraisonAI and praisonai.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonaiagents` | PyPI | All versions | 1.6.40 |
| `praisonaiagents` | PyPI | All versions | 1.6.40 |
| `praisonaiagents` | PyPI | All versions | 1.6.40 |
| `PraisonAI` | PyPI | All versions | 4.6.40 |
| `praisonai` | PyPI | All versions | 4.6.40 |
| `praisonai` | PyPI | All versions | 4.6.40 |

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

Upgrade praisonaiagents to 1.6.40 or later.

## Is CVE-2026-47392 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47392 is a critical code injection vulnerability in MervinPraison < 1.6.40, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47392 exists.

Affected packages and fixed versions:
- praisonaiagents (PyPI): affected all versions; fixed in 1.6.40
- praisonaiagents (PyPI): affected all versions; fixed in 1.6.40
- praisonaiagents (PyPI): affected all versions; fixed in 1.6.40
- PraisonAI (PyPI): affected all versions; fixed in 4.6.40
- praisonai (PyPI): affected all versions; fixed in 4.6.40
- praisonai (PyPI): affected all versions; fixed in 4.6.40

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-47392/ (Markdown: https://insights.sbomify.com/CVE-2026-47392/index.md)
```

## Sources

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

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