<?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://db.gcve.eu</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>Sun, 25 Oct 2026 05:42:12 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-56832</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-56832</link>
      <description>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-56832</guid>
    </item>
    <item>
      <title>GHSA-8579-rgg5-ph2m — PraisonAI DiscordApproval accepts unrelated channel messages as dangerous-tool approvals</title>
      <link>https://db.gcve.eu/vuln/ghsa-8579-rgg5-ph2m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# DiscordApproval accepts unrelated channel messages as dangerous-tool approvals&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`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`.&lt;/p&gt;
&lt;p&gt;The decision is not bound to:&lt;/p&gt;
&lt;p&gt;- a Discord reply to the approval message;
- a Discord thread created for that request;
- a Discord interaction/button callback for that request;
- an explicit approver user allowlist; or
- an approval nonce visible only to intended approvers.&lt;/p&gt;
&lt;p&gt;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 local 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&amp;#39;s unthreaded channel
cross-talk: the approving message does not need to be a reply or otherwise
request-bound.&lt;/p&gt;
&lt;p&gt;## Affected Product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Ecosystem: `pip`
- Package: `praisonai`
- Component: Python messaging approval backends
- Primary affected file: `src/praisonai/praisonai/bots/_discord_approval.py`
- Related sibling files:
  - `src/praisonai/praisonai/bots/_slack_approval.py`
  - `src/praisonai/praisonai/bots/_telegram_approval.py`
- Latest PyPI version validated: `4.6.58`
- Current `origin/main` validated:
  `1ad58ca02975ff1398…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# DiscordApproval accepts unrelated channel messages as dangerous-tool approvals&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`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`.&lt;/p&gt;
&lt;p&gt;The decision is not bound to:&lt;/p&gt;
&lt;p&gt;- a Discord reply to the approval message;
- a Discord thread created for that request;
- a Discord interaction/button callback for that request;
- an explicit approver user allowlist; or
- an approval nonce visible only to intended approvers.&lt;/p&gt;
&lt;p&gt;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 local 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&amp;#39;s unthreaded channel
cross-talk: the approving message does not need to be a reply or otherwise
request-bound.&lt;/p&gt;
&lt;p&gt;## Affected Product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Ecosystem: `pip`
- Package: `praisonai`
- Component: Python messaging approval backends
- Primary affected file: `src/praisonai/praisonai/bots/_discord_approval.py`
- Related sibling files:
  - `src/praisonai/praisonai/bots/_slack_approval.py`
  - `src/praisonai/praisonai/bots/_telegram_approval.py`
- Latest PyPI version validated: `4.6.58`
- Current `origin/main` validated:
  `1ad58ca02975ff1398…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-8579-rgg5-ph2m</guid>
    </item>
    <item>
      <title>PYSEC-2026-3506 — PraisonAI DiscordApproval accepts unrelated channel messages as dangerous-tool approvals</title>
      <link>https://db.gcve.eu/vuln/pysec-2026-3506</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# DiscordApproval accepts unrelated channel messages as dangerous-tool approvals&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`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`.&lt;/p&gt;
&lt;p&gt;The decision is not bound to:&lt;/p&gt;
&lt;p&gt;- a Discord reply to the approval message;
- a Discord thread created for that request;
- a Discord interaction/button callback for that request;
- an explicit approver user allowlist; or
- an approval nonce visible only to intended approvers.&lt;/p&gt;
&lt;p&gt;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 local 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&amp;#39;s unthreaded channel
cross-talk: the approving message does not need to be a reply or otherwise
request-bound.&lt;/p&gt;
&lt;p&gt;## Affected Product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Ecosystem: `pip`
- Package: `praisonai`
- Component: Python messaging approval backends
- Primary affected file: `src/praisonai/praisonai/bots/_discord_approval.py`
- Related sibling files:
  - `src/praisonai/praisonai/bots/_slack_approval.py`
  - `src/praisonai/praisonai/bots/_telegram_approval.py`
- Latest PyPI version validated: `4.6.58`
- Current `origin/main` validated:
  `1ad58ca02975ff1398…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# DiscordApproval accepts unrelated channel messages as dangerous-tool approvals&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`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`.&lt;/p&gt;
&lt;p&gt;The decision is not bound to:&lt;/p&gt;
&lt;p&gt;- a Discord reply to the approval message;
- a Discord thread created for that request;
- a Discord interaction/button callback for that request;
- an explicit approver user allowlist; or
- an approval nonce visible only to intended approvers.&lt;/p&gt;
&lt;p&gt;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 local 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&amp;#39;s unthreaded channel
cross-talk: the approving message does not need to be a reply or otherwise
request-bound.&lt;/p&gt;
&lt;p&gt;## Affected Product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Ecosystem: `pip`
- Package: `praisonai`
- Component: Python messaging approval backends
- Primary affected file: `src/praisonai/praisonai/bots/_discord_approval.py`
- Related sibling files:
  - `src/praisonai/praisonai/bots/_slack_approval.py`
  - `src/praisonai/praisonai/bots/_telegram_approval.py`
- Latest PyPI version validated: `4.6.58`
- Current `origin/main` validated:
  `1ad58ca02975ff1398…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/pysec-2026-3506</guid>
    </item>
  </channel>
</rss>
