Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1amended

PraisonAI: Missing ownership check on DELETE endpoints allows members to delete others' content in Platform API

CVE-2026-57121GHSA-rh39-9c67-59mh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai-platform 0.1.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
  • CVE-2026-57121: 0.33% estimated exploitation activity in the next 30 days; percentile 26.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A workspace member can permanently delete any resource — projects, agents, issues, labels, issue dependencies, and issue-label attachments — created by the workspace owner or other members. All six content DELETE endpoints enforce workspace membership but perform no ownership or role check. A single malicious or compromised member account can wipe an entire workspace's content irreversibly. Details The published role capability matrix explicitly restricts members from modifying others' content: | Capability | Owner | Admin | Member | |---|---|---|---| | Create issues/tasks | ✅ | ✅ | ✅ | | Edit own content | ✅ | ✅ | ✅ | | Edit others' content | ✅ | ✅ | ❌ | The DELETE handlers for all content resources check that the requesting user is a workspace member, but do not verify that the user either created the resource or holds an owner/admin role. The result is that the member role has unrestricted DELETE access over all workspace content regardless of who created it. Confirmed…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-rh39-9c67-59mh

  2. Revision 1 · created ·

    Published from osv record GHSA-rh39-9c67-59mh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57121

Advisory: PraisonAI: Missing ownership check on DELETE endpoints allows members to delete others' content in Platform API
IDs: CVE-2026-57121, GHSA-rh39-9c67-59mh
Record: https://patchnext.com/advisories/cve-2026-57121 (revision 2, source checked 26 Oct 2026, 13:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai-platform 0.1.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai-platform: affected >= 0.1.4, <= 0.1.4; fixed in 0.1.6

## Suggested inspection (read-only)
- `python -m pip show praisonai-platform`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonai-platform.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rh39-9c67-59mh (OSV record GHSA-rh39-9c67-59mh lists affected ranges: PyPI praisonai-platform >=0.1.4 <0.1.6 (fixed))
- Verified: https://github.com/advisories/GHSA-rh39-9c67-59mh (GitHub-reviewed advisory GHSA-rh39-9c67-59mh lists affected ranges: PyPI praisonai-platform >=0.1.4 <=0.1.4)

Commands are suggestions: review each one before running it.

Loading voting…