<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 16 Oct 2026 06:21:51 +0000</lastBuildDate>
    <item>
      <title>GHSA-qvpf-j64c-jmhr — PraisonAI Slack app_mention bypasses configured user/channel authorization</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qvpf-j64c-jmhr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# PraisonAI Slack `app_mention` bypasses configured user/channel authorization&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;PraisonAI&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;- the sender is not in `BotConfig.allowed_users`;
- the channel is not in `BotConfig.allowed_channels`;
- `unknown_user_policy=&amp;#34;deny&amp;#34;` is configured; and
- the same event content is correctly dropped by the normal `message` handler.&lt;/p&gt;
&lt;p&gt;This is a sibling-handler guard-coverage issue. Slack documents
`app_mention` as a distinct event type rather than a `message.*` event, so
deployments subscribed to app mentions can route unauthorized sender input
around the guarded message path.&lt;/p&gt;
&lt;p&gt;## Affected product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Package: `praisonai`
- Component: `src/praisonai/praisonai/bots/slack.py`
- Configuration component: `src/praisonai-agents/praisonaiagents/bots/config.py`&lt;/p&gt;
&lt;p&gt;Confirmed affected:&lt;/p&gt;
&lt;p&gt;```text
v3.11.0  7f37d754a72511a71f7eeaaa8e9f367a5dc45fd8
v3.11.14 44b800df0eddf32dd5242f47da7513e4a3159d76
v3.12.0  51f95ad904a6616b35caede1cd74026ec8f7152c
v4.4.5   9a3363c900fa3be3fce5483be7f6c1f418757ebb
v4.4.6   90b00f9a25ee5c7ccf4b6ab3152700e1881f262d
v4.4.12  7d0657632fc477673153ad116cecf692b454bfa3
v4.5.2   8dd…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# PraisonAI Slack `app_mention` bypasses configured user/channel authorization&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;PraisonAI&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;- the sender is not in `BotConfig.allowed_users`;
- the channel is not in `BotConfig.allowed_channels`;
- `unknown_user_policy=&amp;#34;deny&amp;#34;` is configured; and
- the same event content is correctly dropped by the normal `message` handler.&lt;/p&gt;
&lt;p&gt;This is a sibling-handler guard-coverage issue. Slack documents
`app_mention` as a distinct event type rather than a `message.*` event, so
deployments subscribed to app mentions can route unauthorized sender input
around the guarded message path.&lt;/p&gt;
&lt;p&gt;## Affected product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Package: `praisonai`
- Component: `src/praisonai/praisonai/bots/slack.py`
- Configuration component: `src/praisonai-agents/praisonaiagents/bots/config.py`&lt;/p&gt;
&lt;p&gt;Confirmed affected:&lt;/p&gt;
&lt;p&gt;```text
v3.11.0  7f37d754a72511a71f7eeaaa8e9f367a5dc45fd8
v3.11.14 44b800df0eddf32dd5242f47da7513e4a3159d76
v3.12.0  51f95ad904a6616b35caede1cd74026ec8f7152c
v4.4.5   9a3363c900fa3be3fce5483be7f6c1f418757ebb
v4.4.6   90b00f9a25ee5c7ccf4b6ab3152700e1881f262d
v4.4.12  7d0657632fc477673153ad116cecf692b454bfa3
v4.5.2   8dd…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qvpf-j64c-jmhr</guid>
    </item>
  </channel>
</rss>
