UTC
High

PraisonAI recipe workflow policy can be bypassed by declaring and YAML-approving dangerous tools outside TEMPLATE.yaml

CVE-2026-57142 · GHSA-7qw2-w5rc-37x2 · published 2026-06-18 · updated 2026-07-20

Severity
High
CVSS score
7.8
Chance of exploitation (EPSS)
0.24%
Fixed in
4.6.61
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

If an operator runs an untrusted recipe, or exposes the recipe runner to users who can choose recipe names/URIs, the recipe can self-authorize a default-denied critical shell tool without the operator setting allowdangeroustools=True. Successful exploitation lets the workflow run execute_command with the privileges of the PraisonAI process if the agent reaches the tool call. The exact trigger depends on the workflow and model/tool-call path, but the policy boundary is already bypassed before execution. This can affect both local CLI use and HTTP recipe-runner deployments.

What to do

Upgrade praisonai to 4.6.61 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Normalize and validate the actual workflow tool graph before recipe execution: Parse the selected workflow file before or during checktoolpolicy(). Include workflow.yaml agents..tools, roles..tools, included recipes, and other workflow-resolved tool lists in the dangerous-tool policy. Treat approve: as an operator-supplied approval policy, not a recipe-controlled bypass of the recipe-level dangerous-tool gate. If approve: remains recipe-controlled, ignore dangerous/default-denied tool entries unless the caller passed allowdangeroustools=True or an explicit external policy allowed that exact tool.

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI>= 4.5.87, < 4.6.614.6.61

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].