cve.bz

CVE-2026-56832 mervinpraison praisonai: Incorrect Authorization

8.8 highEPSS 0.1%Fix available

High (8.8) in mervinpraison praisonai. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in praisonai 4.6.59.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-345 Insufficient Verification of Data Authenticity
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • praisonai (PyPI): fixed in 4.6.59

Ask an AI about this CVE

Show the promptExplain CVE-2026-56832 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-56832?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-56832?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-56832 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
MervinPraison PraisonAI>= 4.5.2, < 4.6.59

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8579-rgg5-ph2mPyPIpraisonai>=4.5.2 <4.6.594.6.59
PYSEC-2026-3506PyPIpraisonai>=4.5.2 <4.6.594.6.59

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON