CVE-2026-57121 MervinPraison CVE debrief

Who should care

Administrators and users of PraisonAI, particularly those with member accounts, should assess exposure and update to version 0.1.5 or later. They should also review and restrict access to DELETE endpoints, monitor for suspicious activity, and implement additional security measures to prevent exploitation.

Why it matters

CVE-2026-57121 allows members to delete others' content in PraisonAI due to missing ownership checks on DELETE endpoints, requiring immediate attention from administrators and users.

• A single malicious or compromised member account can wipe an entire workspace's content irreversibly.
• Members can delete others' content without proper authorization.
• Irreversible deletion of projects, agents, issues, labels, issue dependencies, and issue-label attachments.

Technical summary

The vulnerability exists in PraisonAI versions from 0.1.4 to before 0.1.5, where a workspace member can permanently delete any resource created by the workspace owner or other members due to missing ownership checks on DELETE endpoints. This allows a single malicious or compromised member account to wipe an entire workspace's content irreversibly. The vulnerability was patched in version 0.1.5, and administrators and users should assess exposure and update to the patched version. The vulnerability affects PraisonAI workspace members who can delete others' content without proper authorization.

Defensive priority

High

Recommended defensive actions

• Review and update PraisonAI to version 0.1.5 or later
• Restrict access to DELETE endpoints for members
• Monitor for suspicious activity on DELETE endpoints
• Implement additional logging and monitoring for DELETE endpoint usage
• Conduct regular security audits to identify potential vulnerabilities
• Review and update incident response plans to address potential exploitation
• Track changes to workspace content and member activity

Evidence notes

The CVE record and source item provide details on the vulnerability, including its impact and patch information. The vulnerability was patched in version 0.1.5. There are no known exploits, but defenders should verify affected scope and update to the patched version. The source item and CVE record provide further context on the vulnerability and its impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.