CVE-2026-48169
PraisonAI has Cross-Workspace IDOR and Privilege Escalation via Platform API
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.
INFO
Published Date :
Aug. 7, 2026, 10:16 p.m.
Last Modified :
Oct. 23, 2026, 8:10 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | HIGH | [email protected] | ||||
| CVSS 3.1 | HIGH | MITRE-CVE |
Solution
- Update PraisonAI Platform API to version 0.1.4.
- Ensure service layer enforces workspace ownership.
- Verify member management requires owner role.
- Audit resource access controls.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-48169.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-48169 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-48169
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-48169 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-48169 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 23, 2026
Action Type Old Value New Value Added Translation Title: praisonai-platform de MervinPraison, Description: PraisonAI es un sistema de equipos multiagente. Las versiones anteriores a la 0.1.4 de la API de la Plataforma PraisonAI tienen dos fallos de autorización que juntos rompen el aislamiento del espacio de trabajo. La capa de servicio para incidencias y proyectos realiza búsquedas globales por clave primaria sin verificar la propiedad del espacio de trabajo, por lo que cualquier usuario autenticado puede leer, modificar y eliminar recursos en cualquier espacio de trabajo simplemente intercambiando UUIDs en sus solicitudes de API. Además de eso, cada endpoint de gestión de miembros (añadir, actualizar rol, eliminar) solo requiere ’min_role=“member”’, lo que permite a cualquier miembro del espacio de trabajo ascenderse a propietario y expulsar al propietario original. Un miembro con pocos privilegios de un espacio de trabajo puede robar datos de cualquier otro espacio de trabajo y tomar el control de cualquier espacio de trabajo al que pertenezca. Ambos problemas provienen de la misma brecha: la capa de rutas extrae ’workspace_id’ de la URL y verifica la membresía, pero la capa de servicio ignora el alcance del espacio de trabajo para las búsquedas de recursos e ignora el nivel de rol del llamador para las operaciones de miembros. La dependencia ’require_workspace_member()’ hace su trabajo correctamente. El problema es que la capa de servicio no utiliza la información que proporciona. La versión 0.1.4 de la API de la Plataforma PraisonAI aplica un parche al problema. -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Aug. 11, 2026
Action Type Old Value New Value Added Reference https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-gv23-xrm3-8c62 Added SSVC {'id': 'CVE-2026-48169', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'poc'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-08-11T01:16:41.512033Z'} -
New CVE Received by [email protected]
Aug. 07, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'MervinPraison', 'product': 'praisonai-platform', 'versions': [{'status': 'affected', 'version': '< 0.1.4'}]}] 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. Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Added CWE CWE-639 Added CWE CWE-862 Added Reference https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-gv23-xrm3-8c62 Added Reference https://github.com/pypa/advisory-database/tree/main/vulns/praisonai-platform/PYSEC-2026-2935.yaml