CVE-2026-47418 MervinPraison CVE debrief

Who should care

Defenders of PraisonAI Platform, users of versions prior to 0.1.4, and security teams responsible for vulnerability management should be aware of this vulnerability and take immediate action to patch or mitigate. This includes reviewing system deployments, assessing exposure, and implementing compensating controls where necessary.

Technical summary

The PraisonAI Platform has an Insecure Direct Object Reference vulnerability in versions prior to 0.1.4. The project CRUD endpoints (GET / PATCH / DELETE /workspaces/{workspace_id}/projects/{project_id} and GET .../{project_id}/stats) only gate access based on workspace membership (require_workspace_member(workspace_id)), but then resolve project IDs through ProjectService.get(project_id) / update(project_id, ...) / delete(project_id) / get_stats(project_id) without threading workspace_id to constrain the lookup.

Defensive priority

High

Recommended defensive actions

• Patch PraisonAI Platform to version 0.1.4 or later
• Restrict access to project endpoints based on workspace membership and project ownership
• Monitor project endpoints for suspicious activity
• Implement additional access controls to prevent unauthorized project access
• Review system deployments for exposure and assign an owner for follow-up
• Confirm whether affected product deployments exist in managed environments
• Track exceptions and retest remediated assets

Evidence notes

The CVE record was published on 2026-07-21T18:17:00.853Z and was last modified on 2026-07-22T19:17:05.527Z. The NVD entry is currently Deferred. The PraisonAI Platform vulnerability affects versions prior to 0.1.4, and defenders should verify the patch status of their deployments. The CVE details are based on the official CVE record and NVD entry.

Official resources