Owner issue dependency deletion via wrong-endpoint authorization
Published Oct 7, 2026 · Updated Oct 7, 2026
Incorrect authorization in PraisonAI Platform before 0.1.9 allows remote authenticated users to delete owner issue dependencies through the API. The dependency DELETE route accepts either issue in an edge but checks delete permission only against the caller-selected URL issue. A workspace member who owns the related issue can therefore remove an edge on an owner-created issue, altering its workflow relationships without owner or admin authority.
Summary
What happened
Incorrect authorization in PraisonAI Platform before 0.1.9 allows remote authenticated users to delete owner issue dependencies through the API. The dependency DELETE route accepts either issue in an edge but checks delete permission only against the caller-selected URL issue. A workspace member who owns the related issue can therefore remove an edge on an owner-created issue, altering its workflow relationships without owner or admin authority.
The record
- CVE
- CVE-2026-62179
- Published
- Oct 7, 2026
- Updated
- Oct 7, 2026
- Vendor
- PraisonAI
- Product
- PraisonAI Platform
- Classifications
- CWE-863, CWE-862, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2026CVE publishedPublication date reported by the CVE source.
- Oct 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.1.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Published dependency-deletion proof-of-concept scriptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started