Quick answers
- Is CVE-2026-47419 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47419 being exploited in the wild.
- How severe is CVE-2026-47419?
- High severity, with a CVSS score of 8.3, 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-47419?
- 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-47419 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47419?
- 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 Insecure Direct Object Reference (IDOR) exists in the agent CRUD endpoints (`GET / PATCH / DELETE /workspaces/{workspace_id}/agents/{agent_id}`). While the application verifies that the requesting user is a member of the `workspace_id` provided in the URL, the underlying `AgentService.get` method performs a primary-key lookup on `agent_id` without verifying that the agent actually belongs to that specific workspace. An authenticated attacker can exploit this by supplying their own valid `workspace_id` while targeting an `agent_id` belonging to a different workspace. This allows the attacker to read agent configurations (including system prompts and runtime configs), modify agent behavior, or delete agents entirely. The issue is resolved in version 0.1.4 by ensuring the workspace constraint is included in the database query.
Affected products
- MervinPraison praisonai-platform < 0.1.4
Identifiers
- CVE-2026-47419
- GHSA-7p8g-6c6g-h9w7
- PYSEC-2026-2931
Timeline
- 2026-05-19: patched: Fix committed to repository
- 2026-07-21: disclosed: CVE published to NVD