Skip to content

← Actionable
High, CVSS 7.1amended

PraisonAI: Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass

CVE-2026-61442GHSA-c78w-2q4r-68r7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai-platform 0.1.9), 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.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
EPSS
  • CVE-2026-61442: 0.31% estimated exploitation activity in the next 30 days; percentile 24.05 (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.

Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass Summary praisonai-platform lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch leadid to their own user id and then delete the owner-created project, bypassing a delete guard that correctly returned 403 before the reassignment. Technical Details The affected boundary is the difference between "is a workspace member" and "owns or administers this resource". src/praisonai-platform/praisonaiplatform/api/deps.py defines requireworkspacemember, requireworkspaceadmin, requireworkspaceowner, and requiredeletepermission. requireworkspacemember only checks that the caller has at least the member role in the workspace, while requiredeletepermission allows delete only for workspace admins/owners or the resource owner. The project update route in…

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

    Amended from ghsa record GHSA-c78w-2q4r-68r7

  2. Revision 2 · amended ·

    Amended from osv record GHSA-c78w-2q4r-68r7

  3. Revision 1 · created ·

    Published from ghsa record GHSA-c78w-2q4r-68r7

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-61442

Advisory: PraisonAI: Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass
IDs: CVE-2026-61442, GHSA-c78w-2q4r-68r7
Record: https://patchnext.com/advisories/cve-2026-61442 (revision 3, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.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.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai-platform: affected <= 0.1.8; fixed in 0.1.9

## 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://github.com/advisories/GHSA-c78w-2q4r-68r7 (GitHub-reviewed advisory GHSA-c78w-2q4r-68r7 lists affected ranges: PyPI praisonai-platform >=0 <=0.1.8)
- Verified: https://osv.dev/vulnerability/GHSA-c78w-2q4r-68r7 (OSV record GHSA-c78w-2q4r-68r7 lists affected ranges: PyPI praisonai-platform >=0 <0.1.9 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…