CVE-2026-40156: PraisonAI Vulnerable to Implicit Execution of Arbitrary Code via Automatic `tools.py` Loading
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.specfromfilelocation and immediately executes module-level code via spec.loader.execmodule() without explicit user consent, validation, or sandboxing.
Published Apr 10, 2026
Affected packages
praisonai
- Ecosystem
- PyPI
- Affected
- < 4.5.128
- Fixed in
- 4.5.128
- Check
pip show praisonai
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
---
Vulnerable Code Location
src/praisonai/praisonai/tool_resolver.py → ToolResolver._load_local_tools
tools_path = Path(self._tools_py_path) # defaults to "tools.py" in CWD
...
spec = importlib.util.spec_from_file_location("tools", str(tools_path))
module = importlib.util.module_from_spec(spec)
spec.loader.exec_module(module) # Executes arbitrary code---
Reproducing the Attack
- Create a malicious
tools.pyin the target directory:
import os
# Executes immediately on import
print("[PWNED] Running arbitrary attacker code")
os.system("echo RCE confirmed > pwned.txt")
def dummy_tool():
return "ok"- Create any valid
agents.yaml.
- Run:
praisonai agents.yaml- Observe:
[PWNED]is printedpwned.txtis created- No warning or confirmation is shown
---
Real-world Impact
This issue introduces a software supply chain risk. If an attacker introduces a malicious tools.py into a repository (e.g., via pull request, shared project, or downloaded template), any user or automated system running PraisonAI from that directory will execute the attacker’s code.
Affected scenarios include:
- CI/CD pipelines processing untrusted repositories
- Shared development environments
- AI workflow automation systems
- Public project templates or examples
Successful exploitation can lead to:
- Execution of arbitrary commands
- Exfiltration of environment variables and credentials
- Persistence mechanisms on developer or CI systems
---
Remediation Steps
- Require explicit opt-in for loading `tools.py`
- Introduce a CLI flag (e.g.,
--load-tools) or config option - Disable automatic loading by default
- Add pre-execution user confirmation
- Warn users before executing local
tools.py - Allow users to decline execution
- Restrict trusted paths
- Only load tools from explicitly defined project directories
- Avoid defaulting to the current working directory
- Avoid executing module-level code during discovery
- Use static analysis (e.g., AST parsing) to identify tool functions
- Require explicit registration functions instead of import side effects
- Optional hardening
- Support sandboxed execution (subprocess / restricted environment)
- Provide hash verification or signing for trusted tool files
Credited to l3tchupkt.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-61438
PraisonAI vulnerable to Remote Code Execution via Broken AST Sandbox
high7.3Oct 29, 2026CVE-2026-60085
PraisonAI: SecurityPolicy command/path/import restrictions are completely unenforced by the default SubprocessSandbox backend
high8.7Oct 8, 2026CVE-2026-60086
PraisonAI: Prompt-injection defense blocks only when 3+ detector families fire simultaneously; realistic single-vector injections pass through unblocked
medium5.3Oct 8, 2026CVE-2026-60088
PraisonAI: Project custom command templates can read outside-workspace files into model prompts
medium5.5Oct 8, 2026CVE-2026-60090
PraisonAI: PGVector and Cassandra knowledge stores interpolate vector dimensions into DDL
mediumOct 8, 2026CVE-2026-60091
PraisonAI: Jobs API is unauthenticated by default and allows attacker-controlled webhook SSRF
high7.2Oct 8, 2026
