# CVE-2026-56832: PraisonAI DiscordApproval accepts unrelated channel messages as dangerous-tool approvals


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-8579-rgg5-ph2m, PYSEC-2026-3506

## What is CVE-2026-56832?

CVE-2026-56832 is a high-severity vulnerability in MervinPraison PraisonAI, published on 23 Oct 2026. 

### Official description

PraisonAI is a multi-agent teams system. From version 4.5.2 to before version 4.6.59, praisonai.bots.DiscordApproval approves a pending dangerous tool call when it sees any later non-bot message in the configured Discord channel whose text is classified as approval, such as yes. As a result, any user who can post in the configured approval channel can approve a pending high-risk tool call by sending yes after the approval message appears. the same PoV also shows that the Slack and Telegram messaging approval backends have no explicit approver allowlist parameter, but the primary report-grade issue is the Discord backend's unthreaded channel cross-talk: the approving message does not need to be a reply or otherwise request-bound. This issue has been patched in version 4.6.59.

Weakness: CWE-863 (Incorrect Authorization), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-56832?

3 open source packages ship an affected version, including praisonai.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonai` | PyPI | From 4.5.2 | 4.6.59 |
| `praisonai` | PyPI | From 4.5.2 | 4.6.59 |
| `praisonai` | PyPI | From 4.5.2 | 4.6.59 |

## How do I fix CVE-2026-56832?

Upgrade praisonai to 4.6.59 or later.

## Is CVE-2026-56832 being exploited?

There is no known exploitation of CVE-2026-56832 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56832 and fix it if it is affected.

What it is: CVE-2026-56832 is a high-severity vulnerability in MervinPraison PraisonAI, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-56832 in the wild and no public exploit code.

Affected packages and fixed versions:
- praisonai (PyPI): affected from 4.5.2; fixed in 4.6.59
- praisonai (PyPI): affected from 4.5.2; fixed in 4.6.59
- praisonai (PyPI): affected from 4.5.2; fixed in 4.6.59

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56832/ (Markdown: https://insights.sbomify.com/CVE-2026-56832/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56832
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56832
- OSV: https://osv.dev/vulnerability/CVE-2026-56832

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56832/
Summaries are generated and may contain mistakes; the official description above is the record.