CVE-2026-40287

PraisonAI automatically imports ./tools.py from the current working directory when launching certain components. This includes call.py, tool_resolver.py, and CLI tool-loading paths.

A malicious tools.py placed in the process working directory is executed immediately, allowing arbitrary Python code execution in the host environment.

Affected Code

• call.py → import_tools_from_file()
• tool_resolver.py → _load_local_tools()
• tools.py → local tool import flow

PoC

Create tools.py in the directory where PraisonAI is launched:

# tools.py
import os
os.system("echo pwned > /tmp/pwned.txt")

Run any PraisonAI component that loads local tools, for example:

praisonai workflow run safe.yaml

Reproduction Steps

1. Create a malicious tools.py in the current working directory.
2. Start PraisonAI or invoke a CLI command that loads local tools.
3. Verify that /tmp/pwned.txt or the malicious command output exists.

An attacker who can place or influence tools.py in the working directory can execute arbitrary code in the PraisonAI process, compromising the host and any connected data.

Reporter: Lakshmikanthan K (letchupkt)

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2026-40287 has a CVSS score of 8.4 (High). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.5.140, 4.5.139); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-40287? CVE-2026-40287 is a high-severity code injection vulnerability in praisonaiagents (pip), affecting versions <= 1.5.139. It is fixed in 1.5.140, 4.5.139. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2026-40287? CVE-2026-40287 has a CVSS score of 8.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-40287?
   • praisonaiagents (pip) (versions <= 1.5.139)
   • PraisonAI (pip) (versions <= 4.5.138)
4. Is there a fix for CVE-2026-40287? Yes. CVE-2026-40287 is fixed in 1.5.140, 4.5.139. Upgrade to this version or later.
5. Is CVE-2026-40287 exploitable, and should I be worried? Whether CVE-2026-40287 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-40287 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-40287?
   • Upgrade praisonaiagents to 1.5.140 or later
   • Upgrade PraisonAI to 4.5.139 or later