CVE-2026-62179: MervinPraison praisonai-platform · Missing Authorization
Affects MervinPraison praisonai-platformSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.1.9 when convenient.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.1.9
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade praisonai-platform and mervinpraison/praisonai-platform to 0.1.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MervinPraisonpraisonai-platform | Affected
| Fixed in
|
GitHubmervinpraison/praisonai-platformpkg:github/mervinpraison/praisonai-platformOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade praisonai-platform to version 0.1.9 or later, where this authorization issue has been fixed. No other mitigation is indicated or required.
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.