CVE-2026-47418: MervinPraison PraisonAI Platform IDOR in project endpoints

CVE-2026-47418 · 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 outside of their assigned workspace. An authenticated user could view, modify, or delete projects belonging to other organizations or teams by manipulating project identifiers in web requests. This could lead to the unauthorized exposure of sensitive project details, descriptions, and statistics, or the accidental/malicious deletion of another team's work.

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

Quick answers

Is CVE-2026-47418 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47418 being exploited in the wild.
How severe is CVE-2026-47418?
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-47418?
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-47418 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-47418?
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 project CRUD endpoints (GET/PATCH/DELETE) within `src/praisonai-platform/praisonai_platform/api/routes/projects.py`. While the application validates that a user is a member of the `workspace_id` provided in the URL, it fails to verify that the requested `project_id` actually belongs to that workspace. The `ProjectService` performs lookups using only the primary key (`project_id`) without a `workspace_id` predicate. An authenticated attacker can provide their own valid `workspace_id` and a target `project_id` from a different workspace to read, update, or delete project data. This issue is resolved in version 0.1.4 by ensuring resource lookups are scoped to the validated workspace.

Affected products

  • MervinPraison praisonai-platform < 0.1.4

Identifiers

  • CVE-2026-47418
  • GHSA-943m-6wx2-rc2j
  • PYSEC-2026-2932

Timeline

  • 2026-05-19: patched: Fix merged in PR #1685
  • 2026-07-21: disclosed: CVE-2026-47418 published

References

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