Description
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.
Published: 2026-08-07
Score: 8.8 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The PraisonAI Platform API contains two authorization failures that together break workspace isolation. Service‑layer endpoints perform global primary‑key lookups without imposing the workspace boundary, allowing any authenticated user to read, modify, and delete resources in any workspace simply by substituting UUIDs in their requests. Additionally, member‑management endpoints require only a "member" role, enabling any workspace member to promote themselves to owner and remove the original owner. These flaws allow low‑privilege members to exfiltrate data from other workspaces and takeover any workspace they belong to, compromising confidentiality, integrity, and availability.

Affected Systems

The affected product is PraisonAI‑Platform by MervinPraison. All releases prior to version 0.1.4 are vulnerable. The issue manifests on all API routes that perform resource lookups (issues, projects) and on member‑management endpoints that adjust roles. Version 0.1.4 includes a patch that eliminates the missing workspace checks in the service layer and enforces minimum role requirements on member changes.

Risk and Exploitability

With a CVSS score of 8.8 the vulnerability is considered high severity. Exploitation requires an authenticated user with any workspace membership, which is typically available to legitimate users. The attacker can construct API calls that swap UUIDs to access arbitrary resources, and can elevate their role within a workspace. Because the EPSS score is not available, the current exploitation probability is unclear, and the vulnerability is not listed in CISA’s KEV catalog. Nonetheless, the minimal prerequisites and the potential for cross‑workspace data theft imply a significant risk, especially for organizations that expose the API to a large user base.

Generated by OpenCVE AI on August 7, 2026 at 22:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to PraisonAI Platform API version 0.1.4 or later to resolve both the IDOR and privilege‑escalation flaws.
  • Implement stricter access controls on member‑management endpoints, ensuring only members with owner or admin roles can promote or remove other members.
  • If an upgrade cannot be performed immediately, restrict API usage through rate limits, monitor for anomalous UUID substitutions, or temporarily disable globally scoped resource endpoints until the service‑layer checks are restored.

Generated by OpenCVE AI on August 7, 2026 at 22:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-gv23-xrm3-8c62 PraisonAI has Cross-Workspace IDOR and Privilege Escalation via Platform API
History

Fri, 07 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
Description 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.
Title PraisonAI has Cross-Workspace IDOR and Privilege Escalation via Platform API
Weaknesses CWE-639
CWE-862
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-07T21:22:04.197Z

Reserved: 2026-05-20T23:12:43.033Z

Link: CVE-2026-48169

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-07T22:30:03Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization