CVE-2026-56835

8.3High

Published 23 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

8.3CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
Low
User action
None
Impact
High impact on confidentiality, integrity
Weakness
CWE-862, CWE-863

What an attacker gets

Any Slack workspace member can execute commands and trigger PraisonAI agents by mentioning the bot in a channel where it is present. Attackers bypass configured user and channel allowlists, even when an explicit deny policy is set.

Root cause

The Slack bot fails to apply allowed_users, allowed_channels, and unknown-user pairing restrictions within its app_mention event handler.

Affected versions

PraisonAI version 3.11.0 to before version 4.6.59

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Fix & remediation

Upgrade PraisonAI to version 4.6.59 or later. If patching immediately is not possible, remove the bot integration from shared channels or disable the Slack integration.

remediation — bash
$ pip install --upgrade praisonai>=4.6.59

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

PraisonAI is a multi-agent teams system. From version 3.11.0 to before version 4.6.59, PraisonAI's Slack bot applies its configured allowed_users, allowed_channels, and unknown-user pairing policy in the normal Slack message event handler, but not in the adjacent Slack app_mention event handler. A Slack workspace user who can mention the bot in a channel where the Slack app is present can trigger the configured PraisonAI agent even when: the sender is not in BotConfig.allowed_users; the channel is not in BotConfig.allowed_channels; unknown_user_policy="deny" is configured; and the same event content is correctly dropped by the normal message handler. This issue has been patched in version 4.6.59.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-56835