Which versions of PraisonAI Platform are affected by CVE-2026-61441?

PraisonAI Platform contains an authorization flaw that permits workspace members with limited privileges to circumvent permission controls and delete issue dependencies owned by administrators.. A patch is available.

How to fix or mitigate CVE-2026-61441?

24 hours: Assess all PraisonAI Platform deployments for current version and identify affected systems running versions prior to 0.1.9. 7 days: Apply vendor-released patch to upgrade all instances to version 0.1.9 or later; test in staging environment first. 30 days: Conduct audit of issue dependency deletions in the past 90 days to identify any unauthorized changes made during vulnerability window.

PraisonAI Platform CVE-2026-61441

Q: What is the CVSS score of CVE-2026-61441?

CVE-2026-61441 has a CVSS 4.0 base score of 7.1 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-42901 HIGH

Missing Authorization (CWE-862)

2026-07-10 VulnCheck

GHSA-gp44-qpw6-vj4x

Authentication Bypass Praisonai Mervinpraison

7.1

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

7.1 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

4.3 MEDIUM

Network API reachable at low complexity by an authenticated member (PR:L), no UI; impact is limited unauthorized deletion of dependency edges so I:L, with C:N/A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jul 10, 2026 - 15:31 vuln.today

DescriptionCVE.org

PraisonAI Platform (praisonai-platform) before 0.1.9 improperly authorizes deletion of issue dependencies. The DELETE dependency route accepts either endpoint of a dependency edge and checks delete permission only against the caller-selected URL issue. A workspace member who cannot delete a dependency through an owner-created issue endpoint (which returns 403) can delete the same dependency edge by targeting a related member-owned issue endpoint, because permission is validated against the member-owned issue's owner. This allows members to bypass owner/admin authorization and remove owner-created issue dependencies.

AnalysisAI

Broken authorization in PraisonAI Platform before 0.1.9 lets an authenticated workspace member delete owner-created issue dependencies they should not be able to remove. The DELETE dependency route accepts either endpoint of a dependency edge and validates delete permission only against the caller-supplied issue URL, so a member blocked (403) via the owner's issue endpoint can delete the same edge by targeting their own member-owned issue endpoint. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis and it is not on CISA KEV.

Technical ContextAI

The affected component is the PraisonAI Platform (CPE cpe:2.3:a:mervinpraison:praisonai), the web/API server that manages workspaces, issues, and inter-issue dependency edges for the PraisonAI multi-agent framework. The root cause is CWE-862 (Missing Authorization): a dependency edge connects two issues, but the DELETE route evaluates the permission check against whichever issue endpoint the caller selects in the URL rather than against every issue the edge touches. Because a dependency is a symmetric relationship (either endpoint identifies the same edge), the object-level authorization decision becomes attacker-controllable - the caller simply chooses the endpoint whose owner grants them permission, and the check passes.

RemediationAI

Vendor-released patch: upgrade praisonai-platform to 0.1.9 or later, which is the primary and recommended fix; the code change is in commit 846568c7a5d8ce9e71e56e4c213f027c04909753 and documented in advisory GHSA-mxmx-rh57-jx58. If you cannot upgrade immediately, the effective compensating control is to enforce authorization against BOTH endpoints of a dependency edge (deny unless the caller can delete on every issue the edge touches) - where feasible, restrict dependency-deletion to workspace owners/admins at a proxy or policy layer, accepting that this removes members' ability to manage their own legitimate dependencies. Tightening workspace membership (removing untrusted members) reduces the attacker population but does not close the flaw. Advisory URLs: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-mxmx-rh57-jx58 and the patch commit https://github.com/MervinPraison/PraisonAI/commit/846568c7a5d8ce9e71e56e4c213f027c04909753.