PraisonAI Slack Bot Authorization Bypass via App Mentions

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

PraisonAI versions 3.11.0 through 4.6.58 contain an authorization bypass vulnerability in their Slack bot integration. The vulnerability stems from inconsistent enforcement of access controls between two Slack event handlers: while the standard message handler properly validates allowed_users and allowed_channels configurations, the app_mention handler bypasses these restrictions entirely. This means any user in a Slack workspace can invoke the PraisonAI agent by simply mentioning the bot, regardless of whether they're authorized or the channel is approved. Organizations relying on PraisonAI for sensitive multi-agent automation tasks face unauthorized access to their configured agents, potentially leading to data exfiltration, unauthorized command execution, or manipulation of business processes.

Casky's 283 mapped security skills leverage Claude AI's extended reasoning to identify this authorization bypass through the MITRE ATT&CK techniques TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using Casky would observe detection patterns highlighting CWE-862 (Missing Authorization) and CWE-863 (Incorrect Authorization) violations. Specifically, Casky's analysis surfaces inconsistent access control enforcement across application event handlers, detects unauthorized invocation patterns where non-approved users successfully trigger bot functions, and identifies the gap between configured security policies and their actual enforcement across all Slack event pathways. The platform's findings would flag the app_mention handler as an unprotected attack surface and recommend immediate patching to version 4.6.59 or later, plus comprehensive testing of authorization controls across all bot interaction vectors.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-56835.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

identity access management · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-56835

Casky has 283 skills that investigate the attack patterns behind CVE-2026-56835. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn