CVE-2026-55522 — PraisonAI workflow include bypasses tools.py autoload opt-in and executes included recipe code

Affected: MervinPraison PraisonAI, MervinPraison praisonaiagents

PraisonAI is a multi-agent teams system. In versions 3.9.26 through 4.6.57 of praiseonai and 0.12.12 through 1.6.57 of praiseonaiagents, the workflow "include" feature is vulnerable to code execution. Workflow._execute_include() implicitly imports and runs an included recipe's tools.py via a raw importlib.util.spec_from_file_location() and spec.loader.exec_module() call, without honoring the PRAISONAI_ALLOW_TEMPLATE_TOOLS/PRAISONAI_ALLOW_LOCAL_TOOLS autoload opt-in gates or routing through the centralized safe loader that protects the other tools.py autoload paths. As a result, a workflow that includes an attacker-controlled local recipe directory executes arbitrary module-level Python code during include setup, before any child workflow parsing or model call, and the same sink is reachable through the higher-level praisonai.recipe.run() recipe API. An attacker who can cause a victim process to run a workflow or recipe that includes an untrusted local recipe achieves arbitrary Python code execution as the PraisonAI process user, a variant that bypasses the hardening applied to the previously disclosed automatic tools.py RCE advisory family. This issue has been fixed in version 4.6.58 of praisonai and 1.6.58 of praisonaiagents.

GHSA-hxmv-c4g6-5fqc — PraisonAI workflow include bypasses tools.py autoload opt-in and executes included recipe code

Affected: PyPI: praisonaiagents, PyPI: PraisonAI

## Summary

PraisonAI's workflow include implementation implicitly imports and executes an included recipe's `tools.py` file even when the documented `tools.py` autoload opt-in is unset.

This bypasses the hardening added for the prior automatic `tools.py` RCE advisory family. A workflow that includes an untrusted local recipe can execute arbitrary Python module-level code before any model call or child workflow execution.

The same sink is reachable through the higher-level `praisonai.recipe.run()` recipe API when a steps-based recipe workflow includes a local child recipe. The supplementary PoV demonstrates this route without starting a network service or relying on external APIs.

This is distinct from the previously published `tool_resolver.py`, `api/call.py`, `templates/tool_override.py`, and `agents_generator.py` variants. The affected callsite is the workflow include implementation in `praisonaiagents`, reached through the documented/covered `Include` workflow composition feature.

## Affected Components

- Package: `praisonaiagents` - File: `praisonaiagents/workflows/workflows.py` - Sink: `Workflow._execute_include()` - Current affected callsite:

```python tools_py = recipe_path / "tools.py" if tools_py.exists(): spec = importlib.util.spec_from_file_location("recipe_tools", tools_py) recipe_module = importlib.util.module_from_spec(spec) spec.loader.exec_module(recipe_module) ```

The current head also contains a similar unguarded workflow-local `tools.py…

Most recent entries from all

CVE-2026-55522 — PraisonAI workflow include bypasses tools.py autoload opt-in and executes included recipe code

GHSA-hxmv-c4g6-5fqc — PraisonAI workflow include bypasses tools.py autoload opt-in and executes included recipe code