# CVE-2026-48169: PraisonAI has Cross-Workspace IDOR and Privilege Escalation via Platform API

> Authenticated users can access and modify resources in any workspace and escalate privileges to owner due to missing authorization checks in the service layer.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-gv23-xrm3-8c62, PYSEC-2026-2935

## What is CVE-2026-48169?

CVE-2026-48169 is a high-severity missing authorization vulnerability in MervinPraison praisonai-platform, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-48169?

3 open source packages ship an affected version, including praisonai-platform.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonai-platform` | PyPI | All versions | 0.1.4 |
| `praisonai-platform` | PyPI | All versions | 0.1.4 |
| `praisonai-platform` | PyPI | All versions | 0.1.4 |

## How do I fix CVE-2026-48169?

Upgrade praisonai-platform to 0.1.4 or later.

## Is CVE-2026-48169 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48169 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48169 and fix it if it is affected.

What it is: CVE-2026-48169 is a high-severity missing authorization vulnerability in MervinPraison praisonai-platform, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48169 exists.

Affected packages and fixed versions:
- praisonai-platform (PyPI): affected all versions; fixed in 0.1.4
- praisonai-platform (PyPI): affected all versions; fixed in 0.1.4
- praisonai-platform (PyPI): affected all versions; fixed in 0.1.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48169/ (Markdown: https://insights.sbomify.com/CVE-2026-48169/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48169
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48169
- OSV: https://osv.dev/vulnerability/CVE-2026-48169

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48169/
Summaries are generated and may contain mistakes; the official description above is the record.