Is CVE-2026-47417 exploited in the wild?

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

How severe is CVE-2026-47417?

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

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

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

Am I affected by CVE-2026-47417?

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-47417: MervinPraison PraisonAI Platform IDOR in comment endpoints

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

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

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

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

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-47417 · Severity: high · CVSS 8.1 · Published 2026-07-21

PraisonAI Platform, a system for managing multi-agent AI teams, contains a security flaw that allows users to access data from other organizations' workspaces. By exploiting this vulnerability, an authorized user in one workspace can read private comments and post new comments in any other workspace if they know the specific issue ID. This could lead to the exposure of sensitive internal discussions, customer data, or the injection of malicious links into other teams' workflows.

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

Quick answers

Is CVE-2026-47417 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47417 being exploited in the wild.
How severe is CVE-2026-47417?: 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-47417?: 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-47417 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47417?: 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 comment endpoints of the PraisonAI Platform. The application validates that a user belongs to the `workspace_id` provided in the URL path but fails to verify that the requested `issue_id` actually belongs to that workspace. Specifically, `CommentService.create` and `CommentService.list_for_issue` perform database operations using only the `issue_id` without a workspace-scoped join or filter. An authenticated attacker can provide their own valid `workspace_id` to pass the membership check and then supply a target `issue_id` from a different workspace to read or create comments. This vulnerability is patched in version 0.1.4.

Affected products

MervinPraison praisonai-platform < 0.1.4

Identifiers

CVE-2026-47417
GHSA-cp4f-5m9r-5jc2
PYSEC-2026-2933

Timeline

2026-05-19: patched: Fix committed to repository
2026-07-21: disclosed: Security advisory published

References

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