# CVE-2026-47405: PraisonAI Platform missing role checks let any workspace member become owner and take over workspace membership

> Authenticated workspace members can escalate privileges to owner and take over workspace membership due to missing role checks in administrative routes.

- **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:** 21 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-h37g-4h4p-9x97, PYSEC-2026-2936

## What is CVE-2026-47405?

CVE-2026-47405 is a high-severity vulnerability in MervinPraison praisonai-platform, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have a broken workspace authorization check that allows any authenticated low-privilege workspace member to escalate their own role to `owner`. The issue is caused by privileged workspace-management routes using the shared dependency `require_workspace_member(...)` without requiring `admin` or `owner`. The dependency defaults to `min_role="member"`, so routes that should be administrative are accessible to ordinary workspace members. As a result, a normal workspace member can promote their own account from `member` to `owner`; add arbitrary users as `owner` or `admin`; change other members' roles; remove legitimate owners or members; take over workspace membership completely; and/or perform destructive workspace operations after escalation. This is a broken access control / vertical privilege escalation vulnerability. PraisonAI Platform version 0.1.4 patches the issue.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

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

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-47405?

Upgrade praisonai-platform to 0.1.4 or later.

## Is CVE-2026-47405 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47405 is a high-severity vulnerability in MervinPraison praisonai-platform, published on 21 Jul 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-47405 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-47405/ (Markdown: https://insights.sbomify.com/CVE-2026-47405/index.md)
```

## Sources

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

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