Is CVE-2026-47408 exploited in the wild?

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

How severe is CVE-2026-47408?

Medium severity, with a CVSS score of 6.5, 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-47408?

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

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

Am I affected by CVE-2026-47408?

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-47408: MervinPraison PraisonAI Platform IDOR in issue activity endpoint

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

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

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

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

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-47408 · Severity: medium · CVSS 6.5 · Published 2026-07-21

PraisonAI Platform, a system for managing multi-agent AI teams, contains a security flaw that allows users to view activity logs they should not be able to see. A user who is a member of any workspace can access the full history and activity details of issues belonging to other organizations or workspaces. This could lead to the exposure of sensitive operational data, including who performed specific actions and the details of changes made to AI projects.

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

Quick answers

Is CVE-2026-47408 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47408 being exploited in the wild.
How severe is CVE-2026-47408?: Medium severity, with a CVSS score of 6.5, 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-47408?: 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-47408 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47408?: 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 `GET /workspaces/{workspace_id}/issues/{issue_id}/activity` endpoint of the PraisonAI Platform. While the endpoint uses a `require_workspace_member` dependency to verify the requester belongs to the `workspace_id` provided in the URL, the underlying service call `ActivityService.list_for_issue(issue_id)` fails to validate that the requested `issue_id` actually belongs to that workspace. Consequently, an authenticated user can provide their own valid workspace ID and any target issue UUID to retrieve the full activity log for that issue, including actor identities and change details (JSON blobs). This vulnerability is patched in version 0.1.4.

Affected products

MervinPraison PraisonAI Platform < 0.1.4

Identifiers

CVE-2026-47408
GHSA-27p4-pjqv-whgj
PYSEC-2026-2927

Timeline

2026-05-19: patched: Fix committed to main branch
2026-07-21: disclosed: CVE-2026-47408 published

References

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