CVE-2026-47399 MervinPraison CVE debrief

Who should care

Users of PraisonAI Platform versions prior to 0.1.4 should apply patches to prevent unauthorized access, modification, or deletion of objects across workspaces. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure workspace isolation and object ownership.

Technical summary

PraisonAI Platform's workspace-scoped REST routes had an object-level authorization flaw. An authenticated user in one workspace could access, modify, or delete objects from another workspace by providing the victim object's global UUID. This issue was patched in version 0.1.4. The flaw arises from the route layer verifying caller membership in the provided workspace ID, but the service layer resolving the target object by global object ID only, without verifying its workspace ownership.

Defensive priority

High priority due to high CVSS score of 8.8 and potential for significant impact on workspace isolation.

Recommended defensive actions

• Apply PraisonAI Platform version 0.1.4 or later
• Review and update workspace configurations
• Monitor for suspicious activity across workspaces
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

Evidence from official CVE and NVD sources indicate a systemic object-level authorization flaw in PraisonAI Platform versions prior to 0.1.4. The flaw allows an authenticated user from one workspace to access, modify, and delete objects belonging to another workspace by supplying the victim object's global UUID. This issue affects workspace isolation and requires verification of workspace membership and object ownership. Defenders should verify affected product deployments, review official advisories, and plan vendor-supported updates or mitigations.

Official resources