<?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>Sat, 10 Oct 2026 03:51:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-47409 — praisonai-platform: Any workspace member can remove any other member (including the owner) via DELETE /workspaces/{id}/…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-47409</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MervinPraison praisonai-platform&lt;/p&gt;
&lt;p&gt;PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an authorization bypass enabling owner lockout. The `DELETE /workspaces/{workspace_id}/members/{user_id}` endpoint is gated only by `require_workspace_member(workspace_id)` (default `min_role=&amp;#34;member&amp;#34;`). Any member can remove any other member, including the workspace owner, using a single DELETE. There is no caller-role check, no target-role check, no &amp;#34;cannot remove last owner&amp;#34; guard. PraisonAI Platform version 0.1.4 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MervinPraison praisonai-platform&lt;/p&gt;
&lt;p&gt;PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an authorization bypass enabling owner lockout. The `DELETE /workspaces/{workspace_id}/members/{user_id}` endpoint is gated only by `require_workspace_member(workspace_id)` (default `min_role=&amp;#34;member&amp;#34;`). Any member can remove any other member, including the workspace owner, using a single DELETE. There is no caller-role check, no target-role check, no &amp;#34;cannot remove last owner&amp;#34; guard. PraisonAI Platform version 0.1.4 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-47409</guid>
    </item>
    <item>
      <title>GHSA-w388-2392-px73 — praisonai-platform: Missing authorization on member removal enables full workspace takeover by any user regardless of r…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w388-2392-px73</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai-platform&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;**Type:** Authorization bypass enabling owner lockout. The `DELETE /workspaces/{workspace_id}/members/{user_id}` endpoint is gated only by `require_workspace_member(workspace_id)` (default `min_role=&amp;#34;member&amp;#34;`). Any member can remove any other member, including the workspace owner, using a single DELETE. There is no caller-role check, no target-role check, no &amp;#34;cannot remove last owner&amp;#34; guard.
**File:** `src/praisonai-platform/praisonai_platform/api/routes/workspaces.py`, lines 130-140; `services/member_service.py`, lines 71-78.
**Root cause:** `MemberService.remove(workspace_id, user_id)` performs the deletion without any caller-permission check or owner-protection logic. The route accepts the URL-supplied `user_id` and dispatches it straight through. The role hierarchy (`MemberService.has_role`) is implemented but never invoked here. A member-tier attacker can issue `DELETE .../members/&amp;lt;owner_user_id&amp;gt;` and immediately lock the legitimate owner out of the workspace.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;**File 1:** `src/praisonai-platform/praisonai_platform/api/routes/workspaces.py`, lines 130-140.&lt;/p&gt;
&lt;p&gt;```python
@router.delete(&amp;#34;/{workspace_id}/members/{user_id}&amp;#34;, status_code=status.HTTP_204_NO_CONTENT)
async def remove_member(
    workspace_id: str,
    user_id: str,
    user: AuthIdentity = Depends(require_workspace_member),         # &amp;lt;-- BUG: defaults to min_role=&amp;#34;member&amp;#34;
    session: AsyncSession = Depends(get_db),
):
    member_svc = MemberService(session)
    removed = await membe…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai-platform&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;**Type:** Authorization bypass enabling owner lockout. The `DELETE /workspaces/{workspace_id}/members/{user_id}` endpoint is gated only by `require_workspace_member(workspace_id)` (default `min_role=&amp;#34;member&amp;#34;`). Any member can remove any other member, including the workspace owner, using a single DELETE. There is no caller-role check, no target-role check, no &amp;#34;cannot remove last owner&amp;#34; guard.
**File:** `src/praisonai-platform/praisonai_platform/api/routes/workspaces.py`, lines 130-140; `services/member_service.py`, lines 71-78.
**Root cause:** `MemberService.remove(workspace_id, user_id)` performs the deletion without any caller-permission check or owner-protection logic. The route accepts the URL-supplied `user_id` and dispatches it straight through. The role hierarchy (`MemberService.has_role`) is implemented but never invoked here. A member-tier attacker can issue `DELETE .../members/&amp;lt;owner_user_id&amp;gt;` and immediately lock the legitimate owner out of the workspace.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;**File 1:** `src/praisonai-platform/praisonai_platform/api/routes/workspaces.py`, lines 130-140.&lt;/p&gt;
&lt;p&gt;```python
@router.delete(&amp;#34;/{workspace_id}/members/{user_id}&amp;#34;, status_code=status.HTTP_204_NO_CONTENT)
async def remove_member(
    workspace_id: str,
    user_id: str,
    user: AuthIdentity = Depends(require_workspace_member),         # &amp;lt;-- BUG: defaults to min_role=&amp;#34;member&amp;#34;
    session: AsyncSession = Depends(get_db),
):
    member_svc = MemberService(session)
    removed = await membe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w388-2392-px73</guid>
    </item>
  </channel>
</rss>
