CVE-2026-57142
PraisonAI is a multi-agent teams system
- Risk score
- 49/100
- CVSS
- 7.8 v3.1
- Exploit chance (30 days)
- 0.2%
- Published
- 23 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- PraisonAI is a multi-agent teams system. From version 4.5.87 to before version 4.6.61, PraisonAI recipe execution has a dangerous-tool policy that is supposed to block default-denied tools unless the caller explicitly passes allow_dangerous_tools=True. That policy only checks tools declared in TEMPLATE.yaml requires.t…
- Affected
- See advisory
- Fix
- Upgrade the product to 4.6.61 or later.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 7.8 high
References
Original description
PraisonAI is a multi-agent teams system. From version 4.5.87 to before version 4.6.61, PraisonAI recipe execution has a dangerous-tool policy that is supposed to block default-denied tools unless the caller explicitly passes allow_dangerous_tools=True. That policy only checks tools declared in TEMPLATE.yaml requires.tools. For steps-based recipes, the actual execution path loads workflow.yaml with YAMLWorkflowParser. That parser resolves agent-level tools: declarations and preserves top-level approve:. Workflow.start() then installs those YAML-approved tools into the approval context. As a result, an untrusted recipe can omit execute_command from TEMPLATE.yaml requires.tools, declare it in workflow.yaml agents.*.tools, and add top-level approve: [execute_command]. The caller did not set allow_dangerous_tools=True, but the recipe policy allows the recipe and the workflow approval path self-approves the critical shell tool. This issue has been patched in version 4.6.61.
Last activity 23 Oct 2026. Patch Forecast updates every hour.