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

Advisory record · `GHSA-mxmx-rh57-jx58`

- **Identifiers:** `GHSA-mxmx-rh57-jx58` · `CVE-2026-61441` · `CVE-2026-62179` · `PYSEC-2026-4263`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 7 Oct 2026
- **Updated:** 15 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Oct 2026, 14:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `praisonai-platform` (PyPI): affected `<0.1.9`; fixed in `0.1.9`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> PraisonAI Platform (PyPI package praisonai-platform) versions before 0.1.9 are affected. A workspace member can delete a dependency edge that belongs to an owner-created issue by addressing it through a related issue the member created, since the route checks delete permission only against the URL issue. Members can also create dependency edges on owner-created issues. Upgrade to praisonai-platform 0.1.9.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.1 High, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0029, the 21st percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:08 UTC: First seen by agentprime
- 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mxmx-rh57-jx58)

## Sources

- [GitHub Advisory Database: GHSA-mxmx-rh57-jx58](https://github.com/advisories/GHSA-mxmx-rh57-jx58)
- [OSV: GHSA-mxmx-rh57-jx58](https://osv.dev/vulnerability/GHSA-mxmx-rh57-jx58)
- <https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-mxmx-rh57-jx58>
- <https://github.com/MervinPraison/PraisonAI>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-mxmx-rh57-jx58>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mxmx-rh57-jx58/>. Everything for agents: <https://agentprime.io/llms.txt>.