PraisonAI Platform CVE-2026-62179

Exploitation requires a valid authenticated workspace-member account (CVSS PR:L) on a praisonai-platform instance running <= 0.1.8, plus the existence of a dependency edge connecting a member-owned issue to an owner-created issue within the same workspace. The attacker must invoke DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id} using the member-owned issue as the URL issue_id so that require_delete_permission's resource_owner_id check (owner/admin or resource owner) is satisfied against the attacker's own issue. Limiting factors: no anonymous access (membership required), no cross-workspace reach (both issues must be in the same workspace), and a cross-ownership dependency relationship must already exist; impact is confined to deleting dependency edges, with no read access or service disruption.

This is a moderate, authenticated access-control flaw (CWE-862, Missing Authorization), not a high-urgency priority. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, base 6.5) correctly identifies network reachability and low privilege requirements: exploitation requires an authenticated workspace member (PR:L), so this is not an unauthenticated internet-wide threat. No EPSS score, no CISA KEV listing, and no public exploit were supplied in the input, so there is no signal of active or probable near-term exploitation - the evidence is limited to a vendor-issued GitHub Security Advisory (GHSA-mxmx-rh57-jx58) describing the logic flaw. The one point worth flagging is that the input CVSS rates integrity impact as High (I:H); in practice the demonstrated impact is narrow - deletion of dependency edges on owner-created issues that are related to a member-owned issue - which is better characterized as a limited integrity impact. There is no confidentiality or availability impact. Net: a legitimate authorization-boundary bug that platform operators should patch, but it is a 'high-CVSS-leaning-but-constrained-real-risk' issue, gated behind valid workspace membership and the existence of a cross-ownership dependency edge.

An attacker who already holds ordinary workspace-member credentials in a PraisonAI platform instance notices that one of their own member-owned issues is linked by a dependency edge to an owner-created issue's workflow. Although deleting that edge via the owner issue's endpoint returns 403, the member reissues the DELETE against their own member-owned related-issue endpoint, which accepts the same dep_id and checks delete permission only against the member-controlled URL issue, returning 204 and silently removing the owner's dependency. No public proof-of-concept was identified in the provided data, but the advisory describes the exact endpoints and logic needed to reproduce it.