Quick answers
- Is CVE-2026-47412 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47412 being exploited in the wild.
- How severe is CVE-2026-47412?
- High severity, with a CVSS score of 8.1, published 21 July 2026.
- Which products and versions are affected?
- praisonai-platform (PyPI) < 0.1.4, ECOSYSTEM:introduced=0,fixed=0.1.4.
- Is there a fix for CVE-2026-47412?
- 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-47412 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47412?
- 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
An authorization bypass exists in the `DELETE /workspaces/{workspace_id}` endpoint of the PraisonAI Platform. The endpoint is protected by the `require_workspace_member` dependency, which defaults to a `min_role` of "member" rather than "owner." Consequently, any authenticated user with basic member privileges can issue a DELETE request that triggers a cascading database deletion of the workspace and all child entities (projects, agents, issues, etc.) via foreign-key relationships. The vulnerability is exacerbated by the lack of a soft-delete mechanism or confirmation tokens. The issue is addressed in version 0.1.4 by enforcing a "owner" role requirement for this destructive operation.
Affected products
- MervinPraison praisonai-platform <= 0.1.2
Identifiers
- CVE-2026-47412
- GHSA-g8rr-7rj2-f627
- PYSEC-2026-2934
Timeline
- 2026-05-19: patched: Fix merged in PR #1686
- 2026-05-19: advisory: GitHub Advisory GHSA-g8rr-7rj2-f627 published
- 2026-07-21: disclosed: CVE-2026-47412 published to NVD