CVE-2026-48169

Received Received - Intake

Authorization Bypass in PraisonAI Platform API

Publication date: 2026-08-07

Last updated on: 2026-08-07

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-07

Last Modified

2026-08-07

Generated

2026-08-08

AI Q&A

2026-08-08

EPSS Evaluated

N/A

NVD

CVE-2026-48169

Affected Vendors & Products

Vendor	Product	Version / Range
praisonai	praisonai_platform_api	to 0.1.4 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

Executive Summary

This vulnerability affects PraisonAI versions before 0.1.4. It involves two authorization failures that break workspace isolation. First, the service layer allows global lookups of issues and projects without checking workspace ownership, letting any authenticated user access or modify resources in any workspace by changing UUIDs in API requests. Second, member management endpoints only require a minimum role of member, allowing any member to promote themselves to owner and remove the original owner. This lets low-privilege users steal data across workspaces and take over any workspace they belong to.

Detection Guidance

This vulnerability involves improper authorization checks in the PraisonAI Platform API. To detect it, inspect API requests for workspace UUID manipulation and unauthorized role changes. Check logs for requests bypassing workspace isolation or member role promotions without proper permissions.

Impact Analysis

An attacker with basic access could read, modify, or delete sensitive data across all workspaces, not just their own. They could also take control of entire workspaces by promoting themselves to owner and removing legitimate owners, leading to data theft, unauthorized changes, or service disruption. The impact includes loss of confidentiality, integrity, and availability of workspace resources.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection and access control. GDPR requires strict access controls and data isolation, which this flaw undermines by allowing unauthorized access across workspaces. HIPAA mandates safeguards for protected health information, which could be compromised if unauthorized users gain access to sensitive data. Non-compliance risks include fines, legal action, and reputational damage.

Mitigation Strategies

Upgrade PraisonAI to version 0.1.4 or later to patch the authorization failures. Ensure all workspaces are reviewed for unauthorized changes or data access after upgrade.

Hi! I’m here to help you understand CVE-2026-48169. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70