UTC
High

PraisonAI DiscordApproval accepts unrelated channel messages as dangerous-tool approvals

CVE-2026-56832 · GHSA-8579-rgg5-ph2m · published 2026-06-18 · updated 2026-07-20

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

If an application uses DiscordApproval for dangerous tools such as shell commands, file writes, deletes, deployments, or other privileged operations, a low-privileged Discord user with write access to the configured approval channel can approve pending dangerous tool executions. This can lead to code execution, file modification, deployment changes, or data access with the privileges of the PraisonAI process, depending on which tools the agent exposes behind approval. The attacker does not need the LLM API key, shell access, repository access, or PraisonAI process access.

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.

Recommended fixes: 1. For Discord, require approvals to be tied to the request, not merely any later channel message. Use Discord interactions/buttons with opaque server-side request ids, or require a Discord reply whose messagereference.messageid matches the approval message. 2. Add explicit approver identity configuration to all messaging approval backends, for example approveruserids or allowed_approvers. 3. Reject approvals from users outside the configured approver set, even if the message appears in the configured channel. 4. Include a per-request nonce or opaque approval id in callbacks and verify it server side before returning ApprovalDecision(approved=True). 5.

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI>= 4.5.2, <= 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].