Threat Intelligence Database

PraisonAI is a multi-agent teams system. In `praisonai-platform` prior to version 0.1.9, issue dependency deletion can be authorized against the wrong side of a dependency edge. A workspace member cannot delete a dependency through the owner-created issue endpoint, but can delete the same dependency through a member-owned related issue endpoint because the route accepts either endpoint and checks delete permission only against the caller-selected URL issue. Version 0.1.9 patches the issue.

PraisonAI is a multi-agent teams system. Versions prior to 0.1.4 of the PraisonAI Platform API have two authorization failures that together break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, so any authenticated user can read, modify, and delete resources in any workspace just by swapping UUIDs in their API requests. On top of that, every member management endpoint (add, update role, remove) only requires `min_role="member"`, which lets any workspace member promote themselves to owner and kick out the original owner. A low-privilege member of one workspace can steal data from every other workspace and take over any workspace they belong to. Both issues come from the same gap: the route layer pulls `workspace_id` from the URL and verifies membership, but the service layer ignores the workspace scope for resource lookups and ignores the caller's role level for member operations. The `require_workspace_member()` dependency does its job correctly. The problem is that the service layer doesn't use the information it provides. Version 0.1.4 of the PraisonAI Platform API patch the issue.

PraisonAI Platform versions prior to 0.1.4 contain an authorization bypass vulnerability due to insecure direct object references in agent CRUD endpoints. Users who are members of any workspace can access agents belonging to other workspaces by manipulating agent IDs without proper workspace validation. This allows unauthorized reading, modification, or deletion of agents across workspaces. Version 0.1.4 addresses this issue.

CVE-2026-47418 is an authorization bypass vulnerability in the PraisonAI Platform prior to version 0.1.4. The platform's project-related endpoints check only workspace membership but do not properly constrain project access by workspace, allowing users to access projects in other workspaces. This insecure direct object reference (IDOR) flaw permits unauthorized reading, modification, deletion, or statistics viewing of projects outside a user's workspace.

PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an Insecure Direct Object Reference. The comment endpoints (`POST /workspaces/{workspace_id}/issues/{issue_id}/comments` and `GET .../comments`) gate access on `require_workspace_member(workspace_id)` only, then call `CommentService.create(issue_id=issue_id, ...)` and `CommentService.list_for_issue(issue_id)` without verifying that `issue_id` belongs to `workspace_id`. A user who is a member of any workspace `W1` can read every comment on, and post new comments to, any issue in any other workspace `W2`. PraisonAI Platform version 0.1.4 patches the issue.

PraisonAI Platform versions prior to 0.1.4 contain a vulnerability allowing vertical privilege escalation via the workspace member role update endpoint. The API endpoint for updating member roles does not properly verify that the caller has sufficient privileges or restricts role elevation, enabling unauthorized users to promote themselves or others to higher roles. Version 0.1.4 addresses this issue.

PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an Insecure Direct Object Reference. The issue CRUD endpoints (`GET / PATCH / DELETE /workspaces/{workspace_id}/issues/{issue_id}`) gate access on `require_workspace_member(workspace_id)` only, then resolve `issue_id` through `IssueService.get(issue_id)` which is a primary-key lookup with no workspace constraint. A user who is a member of any workspace `W1` can read, modify, or delete issues that belong to a different workspace `W2`. PraisonAI Platform version 0.1.4 patches the issue.

CVE-2026-47414 is an authorization bypass vulnerability in the PraisonAI Platform prior to version 0.1.4. The issue arises because five label-related API endpoints only verify workspace membership but do not confirm that the label_id or issue_id parameters belong to the specified workspace. This allows unauthorized access to labels and issues across workspaces. The vulnerability is fixed in version 0.1.4.

CVE-2026-47413 is a critical privilege escalation vulnerability in the PraisonAI Platform prior to version 0.1.4. The vulnerability allows a user with minimal workspace privileges to escalate their role to owner by exploiting insufficient permission checks in the member addition API endpoint. This enables unauthorized privilege escalation and potential cross-tenant member injection. The issue is patched in version 0.1.4.

PraisonAI Platform versions prior to 0.1.4 contain an authorization bypass vulnerability in the DELETE /workspaces/{workspace_id} endpoint. Any workspace member, regardless of role, can delete the entire workspace and all associated data without additional authorization checks or recovery options. This issue is fixed in version 0.1.4.