Quick answers
- Is CVE-2026-47405 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47405 being exploited in the wild.
- How severe is CVE-2026-47405?
- High severity, with a CVSS score of 8.8, published 21 July 2026.
- Which products and versions are affected?
- praisonai-platform (PyPI) <= 0.1.2, ECOSYSTEM:introduced=0,fixed=0.1.4.
- Is there a fix for CVE-2026-47405?
- Yes. praisonai-platform (PyPI): upgrade to 0.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47405 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47405?
- Check whether you run praisonai-platform (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- praisonai-platform (PyPI): upgrade to 0.1.4 or later
pip install "praisonai-platform>=0.1.4"
Technical details
A vertical privilege escalation vulnerability exists in PraisonAI Platform due to improper authorization checks in workspace management routes. The `require_workspace_member` dependency in `praisonai_platform/api/deps.py` defaults to a `min_role` of 'member'. Several administrative endpoints in `workspaces.py` (including PATCH, POST, and DELETE methods for workspace and member management) utilize this dependency without overriding the default role requirement. Consequently, any authenticated user with basic workspace access can call these endpoints to modify their own role to 'owner', add new owners, or remove existing members, including the original workspace creator. The issue is resolved in version 0.1.4 by enforcing stricter role requirements (admin/owner) on management routes.
Affected products
- MervinPraison PraisonAI Platform < 0.1.4
Identifiers
- CVE-2026-47405
- GHSA-h37g-4h4p-9x97
- PYSEC-2026-2936
Timeline
- 2026-05-19: patched: Fix committed and advisory published by maintainer
- 2026-07-21: disclosed: CVE published to NVD