Is CVE-2026-47414 exploited in the wild?

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

How severe is CVE-2026-47414?

High severity, with a CVSS score of 7.6, 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-47414?

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

It is attacked over the network, in a software library.

Am I affected by CVE-2026-47414?

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-47414: MervinPraison PraisonAI Platform IDOR in label endpoints

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

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

It is attacked over the network, in a software library.

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

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

PraisonAI Platform, a system for managing multi-agent AI teams, contains a security flaw in how it handles labels and issues within workspaces. An authenticated user can modify, delete, or reassign labels and issues belonging to other users' workspaces by manipulating ID numbers in web requests. This could lead to unauthorized data modification, loss of organizational labels, and corruption of project tracking across different customer accounts.

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

Quick answers

Is CVE-2026-47414 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47414 being exploited in the wild.
How severe is CVE-2026-47414?: High severity, with a CVSS score of 7.6, 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-47414?: 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-47414 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-47414?: 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 PraisonAI Platform's label management endpoints, including PATCH, DELETE, and POST operations for labels and issues. The root cause is that while the application verifies the requester is a member of the workspace ID provided in the URL, it fails to verify that the specific label_id or issue_id provided also belongs to that workspace. The LabelService and associated route handlers pass these IDs directly to database queries without workspace-level scoping. An authenticated attacker can exploit this to modify or delete labels, or link/unlink labels to issues across different workspaces, provided they can guess or obtain the target object IDs. The issue is fixed in version 0.1.4.

Affected products

MervinPraison praisonai-platform < 0.1.4

Identifiers

CVE-2026-47414
GHSA-5jx9-w35f-vp65
PYSEC-2026-2929

Timeline

2026-05-19: patched: Fix merged in commit ef79b7a
2026-07-21: disclosed: CVE-2026-47414 published

References

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