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.
CVE-2026-47392
This critical-severity CVE scores 9.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.9
- EG Score
- 9.9(low)
- EPSS
- 45.1%
- KEV
- Not listed
Published
May 29, 2026
Last Modified
July 21, 2026
Advisory Details (3)
Auto-updated Jul 21, 2026Sandbox escape via `print.__self__` builtins module leak in `execute_code` (subprocess mode) · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4mr5-g6f9-cfrhrefactor: security batch — 10 hardening fixes
Patch available: MervinPraison/PraisonAI v4.6.126 (PR #1684 merged 2026-05-19)
https://github.com/MervinPraison/PraisonAI/pull/1684commit b0d8f777528f (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.126 (contains commit b0d8f777528f)
https://github.com/MervinPraison/PraisonAI/commit/b0d8f777528f3253a0cfb0a3ef65455da6ae32f6Vendor Advisories for CVE-2026-47392(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
PyPI(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| praisonai | 0.0.1 ... 4.6.9 (731 versions) | 4.6.40 | — |
| praisonaiagents | 0.0.1 ... 1.6.9 (568 versions) | 1.6.40 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 1× in last 7d / 1× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-29 23:13 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-47392?
When was CVE-2026-47392 disclosed?
Is CVE-2026-47392 actively exploited?
What is the CVSS score of CVE-2026-47392?
How do I remediate CVE-2026-47392?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47392
Is Your Infrastructure Affected by CVE-2026-47392?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.