CVE-2026-40156 json
PraisonAI Affected by Implicit Execution of Arbitrary Code via Automatic `tools.py` Loading
published 2026-04-10 6 mo ago modified 2026-10-26 13 d ago also EUVD-2026-21508 , GHSA-2g3w-cpc4-chr4 , PYSEC-2026-2895
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
PraisonAI is a multi-agent teams system. Prior to 4.5.128, PraisonAI automatically loads a file named tools.py from the current working directory to discover and register custom agent tools. This loading process uses importlib.util.spec_from_file_location and immediately executes module-level code via spec.loader.exec_module() without explicit user consent, validation, or sandboxing. The tools.py file is loaded implicitly, even when it is not referenced in configuration files or explicitly requested by the user. As a result, merely placing a file named tools.py in the working directory is sufficient to trigger code execution. This behavior violates the expected security boundary between user-controlled project files (e.g., YAML configurations) and executable code, as untrusted content in the working directory is treated as trusted and executed automatically. If an attacker can place a malicious tools.py file into a directory where a user or automated system (e.g., CI/CD pipeline) runs praisonai, arbitrary code execution occurs immediately upon startup, before any agent logic begins. This vulnerability is fixed in 4.5.128.
Patch / fix
- pypi praisonai 4.5.128
- praison praisonai 4.5.128
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 6 mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-2g3w-cpc4-chr4 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | praisonai | <4.5.128 |
4.5.128 |
Affected products
- MervinPraison PraisonAI
Classification
References
-
github.com
/MervinPraison/PraisonAI/security/advisories/GHSA-2g3w-cpc4-chr4
exploit, web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-40156
advisory
-
github.com
/MervinPraison/PraisonAI
package
-
github.com
/MervinPraison/PraisonAI/releases/tag/v4.5.128
web
-
pypi.org
/project/praisonai
package
-
github.com
/advisories/GHSA-2g3w-cpc4-chr4
advisory
Sources
- CVE List CVE-2026-40156
- GitHub Advisory GHSA-2g3w-cpc4-chr4
- NVD CVE-2026-40156
- OSV PYSEC-2026-2895
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.