Is CVE-2026-47415 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47415 being exploited in the wild.

How severe is CVE-2026-47415?

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-47415?

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-47415 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-47415?

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.

CVE-2026-47415: MervinPraison PraisonAI Platform IDOR in issue endpoints

Q: Is there a fix for CVE-2026-47415?

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.

Q: How is CVE-2026-47415 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-47415?

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.

CVE-2026-47415 · Severity: high · CVSS 8.3 · Published 2026-07-21

PraisonAI Platform, a system for managing multi-agent AI teams, contains a security flaw that allows users to access data belonging to other organizations or teams. By exploiting this vulnerability, an authorized user in one workspace can view, modify, or delete issues and tasks in any other workspace if they know the specific ID of that item. This could lead to the exposure of confidential project details, unauthorized changes to internal roadmaps, or the permanent deletion of team data.

Technologies: praisonai-platform (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-47415 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47415 being exploited in the wild.
How severe is CVE-2026-47415?: 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-47415?: 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-47415 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47415?: 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 issue CRUD endpoints (`GET / PATCH / DELETE /workspaces/{workspace_id}/issues/{issue_id}`). While the application verifies that a user is a member of the `workspace_id` provided in the URL, the underlying `IssueService` performs lookups using only the `issue_id` primary key without enforcing a workspace ownership constraint. Consequently, an authenticated user belonging to any workspace can manipulate issues in a different workspace by supplying their own valid workspace ID in the path and the target issue's UUID in the object parameter. This allows for unauthorized reading of issue descriptions, modification of project assignments, and deletion of records. The issue is resolved in version 0.1.4 by threading the workspace constraint through the service layer.

Affected products

MervinPraison praisonai-platform < 0.1.4

Identifiers

CVE-2026-47415
GHSA-xwq8-frcg-77q8
PYSEC-2026-2939

Timeline

2026-05-19: patched: Fix committed to repository
2026-07-21: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.