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

> Workspace members can delete issue dependencies owned by others by exploiting incorrect authorization checks on related issue endpoints.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026

## What is CVE-2026-62179?

CVE-2026-62179 is a medium-severity missing authorization vulnerability in MervinPraison praisonai-platform, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PraisonAI is a multi-agent teams system. In `praisonai-platform` prior to version 0.1.9, 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. Version 0.1.9 patches the issue.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-62179?


## How do I fix CVE-2026-62179?

Upgrade to a fixed version.

## Is CVE-2026-62179 being exploited?

There is no known exploitation of CVE-2026-62179 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62179 and fix it if it is affected.

What it is: CVE-2026-62179 is a medium-severity missing authorization vulnerability in MervinPraison praisonai-platform, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62179 in the wild and no public exploit code.

Affected product: MervinPraison praisonai-platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62179/ (Markdown: https://insights.sbomify.com/CVE-2026-62179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62179
- OSV: https://osv.dev/vulnerability/CVE-2026-62179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62179/
Summaries are generated and may contain mistakes; the official description above is the record.