Skip to content

← Actionable
Medium, CVSS 6.5amended

PraisonAI: Platform members can delete owner issue dependencies through member-owned related issues

CVE-2026-62179GHSA-mxmx-rh57-jx58

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
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS
  • CVE-2026-61441: 0.29% estimated exploitation activity in the next 30 days; percentile 21.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
  • CVE-2026-62179: 0.18% estimated exploitation activity in the next 30 days; percentile 6.97 (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 members can delete owner issue dependencies through member-owned related issues Summary praisonai-platform issue dependency deletion can be authorized against the wrong side of a dependency edge. A workspace member cannot delete a dependency through the owner-created issue endpoint, but can delete the same dependency through a member-owned related issue endpoint because the route accepts either endpoint and checks delete permission only against the caller-selected URL issue. Technical Details The affected boundary is the difference between ordinary workspace membership and owner/admin authority over destructive changes to owner-created issue workflow state. src/praisonai-platform/praisonaiplatform/api/routes/dependencies.py defines DELETE /workspaces/{workspaceid}/issues/{issueid}/dependencies/{depid}. The route first verifies that the URL issueid is in the workspace, loads the dependency by depid, and accepts the dependency when either dep.issueid == issueid or…

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

    Amended from ghsa record GHSA-mxmx-rh57-jx58

  2. Revision 2 · amended ·

    Amended from osv record GHSA-mxmx-rh57-jx58

  3. Revision 1 · created ·

    Published from ghsa record GHSA-mxmx-rh57-jx58

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

Advisory: PraisonAI: Platform members can delete owner issue dependencies through member-owned related issues
IDs: CVE-2026-62179, GHSA-mxmx-rh57-jx58
Record: https://patchnext.com/advisories/cve-2026-62179 (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: Medium (CVSS 6.5)
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-mxmx-rh57-jx58 (GitHub-reviewed advisory GHSA-mxmx-rh57-jx58 lists affected ranges: PyPI praisonai-platform >=0 <=0.1.8)
- Verified: https://osv.dev/vulnerability/GHSA-mxmx-rh57-jx58 (OSV record GHSA-mxmx-rh57-jx58 lists affected ranges: PyPI praisonai-platform >=0 <0.1.9 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…