CVE-2026-56835 — PraisonAI Slack app_mention bypasses configured user/channel authorization
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (high)+6
- CISA SSVC: exploitation "poc"+5
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Pip Praisonai: fixed in version 4.6.59 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (MervinPraison PraisonAI, Pip Praisonai).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| MervinPraison | PraisonAI | version >= 3.11.0, < 4.6.59 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Pip | Praisonai | ≥ 3.11.0 and ≤ 4.6.58 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.3 | CVSS 3.1 | High | 2.8 | 5.5 | security-advisories@github.com via NIST National Vulnerability Database |
| 8.3 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.3 | CVSS 3.1 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 24, 2026 → Oct 29, 2026 · 6 reading(s) · max 0.37%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Fix documented
- Affected products added · pip/praisonai
- Affected products added · mervinpraison/praisonai
- Record published
- CVSS changed · 8.3
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 23, 2026 – Oct 23, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-57144 PraisonAI SandlockSandbox falls back to unrestricted subprocess execution when Landlock is unavailable 7d
- High CVE-2026-57121 PraisonAI: Missing ownership check on DELETE endpoints allows members to delete others' content in Platform API 7d
- High CVE-2026-57142 PraisonAI recipe workflow policy can be bypassed by declaring and YAML-approving dangerous tools outside TEMPLATE.yaml 7d
- High CVE-2026-57146 PraisonAI A2U incomplete authentication fix leaves current serve command unauthenticated by default 7d
- High CVE-2026-57114 PraisonAI: Jobs webhook SSRF protection bypass via DNS rebinding 7d
- High CVE-2026-57117 PraisonAI: Compute-bridged file tools allow shell command injection 7d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-56835 is "PraisonAI Slack app_mention bypasses configured user/channel authorization", rated High. It affects PraisonAI (MervinPraison); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.3 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.