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
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.
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | >= 4.5.87, < 4.6.61 | 4.6.61 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- CriticalPraisonAI: AICoder Arbitrary File Write and Command Execution via LLM Tool Callspraisonai
- CriticalPraisonAI: Code Injection via f-string Interpolation in Deploy API Server Generationpraisonai
- CriticalPraisonAI has a Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92praisonai
- CriticalPraisonAI: Arbitrary File Read/Write via `multiedit` Tool Without Path Validationpraisonai
- CriticalPraisonAI: Unauthenticated RCE via Jobs API + Approval Bypasspraisonaiagents, praisonai
- CriticalPraisonAI: AgentOS remains unauthenticated after incomplete fix version and allows remote agent invocationpraisonai
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.