# CVE-2026-47399: PraisonAI Platform workspace-scoped routes allow cross-workspace object access by global object ID

> Authenticated users can access, modify, or delete objects in other workspaces by supplying global UUIDs, breaking workspace isolation.

- **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:** 22 Jul 2026
- **Also known as:** GHSA-6h6v-6m7w-7vxx, PYSEC-2026-2930

## What is CVE-2026-47399?

CVE-2026-47399 is a high-severity missing authorization 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. Prior to version 0.1.4, the workspace-scoped REST routes contain a systemic object-level authorization flaw that allows an authenticated user from one workspace to access, modify, and delete objects belonging to another workspace by supplying the victim object's global UUID. The affected pattern appears in workspace-scoped routes such as agents, projects, issues, and comments. The route layer verifies that the caller is a member of the `workspace_id` provided in the URL, but the service layer later resolves the target object by global object ID only. It does not verify that the resolved object actually belongs to the workspace in the URL. As a result, a valid member of `workspace_attacker` can call a route under `/api/v1/workspaces/{workspace_attacker}/...` while supplying an object UUID from `workspace_victim`. The server authorizes the request based on membership in `workspace_attacker`, then fetches or mutates the victim object by global UUID. This breaks the platform's workspace isolation boundary. PraisonAI Platform version 0.1.4 patches the issue.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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

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

Upgrade praisonai-platform to 0.1.4 or later.

## Is CVE-2026-47399 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47399 is a high-severity missing authorization 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-47399 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-47399/ (Markdown: https://insights.sbomify.com/CVE-2026-47399/index.md)
```

## Sources

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

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