UTC
High

PraisonAI recipe serve Typer command bypasses the non-localhost authentication guard

CVE-2026-56836 · GHSA-5qw8-f2g9-ff29 · published 2026-06-18 · updated 2026-07-20

Severity
High
CVSS score
8.2
Chance of exploitation (EPSS)
0.33%
Fixed in
4.6.59
  • Exploitation Public proof of concept
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

If an operator follows the vulnerable command path on a reachable interface, any network caller that can reach the Recipe HTTP server can access recipe runner endpoints without credentials. Affected endpoints include: GET /v1/recipes POST /v1/recipes/run POST /v1/recipes/stream POST /v1/recipes/validate optional POST /admin/reload when admin endpoints are enabled The exact impact depends on configured recipes and deployment context. At a minimum, an attacker can enumerate recipes and trigger recipe validation or execution flows intended for local or authenticated callers.

What to do

Upgrade praisonai to 4.6.59 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.

Prefer one canonical Recipe server CLI path and enforce the same preflight for every wrapper. Recommended changes: 1. Remove or hard-disable the deprecated Typer praisonai recipe serve command, or make it delegate to the hardened RecipeHandler.cmdserve() code path. 2. Add the same non-localhost/no-auth guard to cli/commands/recipe.py. 3. Treat PRAISONAIAPIKEY as a secret only when auth=api-key is selected; do not rely on the env var's presence alone unless the command also enables auth explicitly. 4. Fix the deprecated command's help examples so remote binding always includes auth. 5. Consider changing --cors default from to no CORS or localhost origins. 6.

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI>= 4.5.112, <= 4.6.584.6.59

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].