PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Prior to version 0.1.4, the Platform server exposes resources under /api/v1/workspaces/{workspace_id}/... and protects them with a require_workspace_member(workspace_id) FastAPI dependency. The dependency only checks that the caller is a member of the workspace_id in the URL prefix. The route handlers then look up the inner resource (agent_id, issue_id, project_id, label_id, comment_id, dependency_id) by primary key alone. The resource's own workspace_id is never compared to the URL's workspace_id. A user can therefore put their own workspace in the URL prefix and any other workspace's resource ID in the path. The auth check passes, since they really are a member of the prefix workspace. The service then returns the cross-tenant resource for read, update, or delete. There is a second bug in the member-management routes (add_member, update_member_role, remove_member, update_workspace, delete_workspace). Each one inherits the default min_role="member" from require_workspace_member. Any basic member can therefore promote themselves to admin or owner, demote or remove other members, and delete the workspace. The role hierarchy exists in the schema but is not enforced. Registration is open at /api/v1/auth/register with no email verification. The default server bind is 0.0.0.0:8000 (python -m praisonai_platform). One curl from any unauthenticated network position is enough to bootstrap into the system. PraisonAI Platform version 0.1.4 patches the issue.
CVE-2026-47407
This critical-severity CVE scores 9.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.4
- EG Score
- 9.4(low)
- EG Risk
- —
- EPSS
- 14.9%
- KEV
- Not listed
Published
May 29, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Jul 21, 2026Cross-workspace IDOR + member-role privilege escalation in PraisonAI Platform · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-h8q5-cp56-rr65refactor: security batch 3 — platform service scoping (do not auto-merge)
Patch available: MervinPraison/PraisonAI v4.6.126 (PR #1686 merged 2026-05-19)
https://github.com/MervinPraison/PraisonAI/pull/1686commit 24385d648765 (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.126 (contains commit 24385d648765)
https://github.com/MervinPraison/PraisonAI/commit/24385d64876577620f749957bd4814f162f4ca47Vendor Advisories for CVE-2026-47407(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| praisonai-platform | 0.1.0, 0.1.1, 0.1.2, 0.1.3 | 0.1.4 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 17:04 UTCEG score recompute▲ 9.40
- 2026-07-21 17:03 UTCMITRE cvelistV5CVSS v3 → 9.4 · CVSS v4 → 9.4
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-29 23:13 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-269 · CWE-863
Frequently asked(5)
What is CVE-2026-47407?
When was CVE-2026-47407 disclosed?
Is CVE-2026-47407 actively exploited?
What is the CVSS score of CVE-2026-47407?
How do I remediate CVE-2026-47407?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47407
Is Your Infrastructure Affected by CVE-2026-47407?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.