Quick answers
- Is CVE-2026-47399 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47399 being exploited in the wild.
- How severe is CVE-2026-47399?
- 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-47399?
- 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-47399 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47399?
- 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
The PraisonAI Platform (prior to version 0.1.4) suffers from an Insecure Direct Object Reference (IDOR) vulnerability due to a failure to bind workspace membership authorization with object ownership validation. While the route layer verifies that a user is a member of the 'workspace_id' provided in the REST URL, the underlying service layer resolves target objects (such as agents, projects, issues, and comments) using only their global UUID. Because the service layer does not verify that the resolved object actually belongs to the workspace specified in the URL, an authenticated attacker can perform CRUD operations on any object across the platform if they know its UUID. This was patched in version 0.1.4 by enforcing workspace-scoped lookups in the service layer.
Affected products
- MervinPraison PraisonAI Platform < 0.1.4
Identifiers
- CVE-2026-47399
- GHSA-6h6v-6m7w-7vxx
- PYSEC-2026-2930
Timeline
- 2026-05-19: patched: Fix committed in version 0.1.4
- 2026-07-21: disclosed: CVE-2026-47399 published