Vulnerability in praisonai-platform (CVE-2026-62179)
Summary
Vulnerability in praisonai-platform (CVE-2026-62179). Data can be tampered with by attackers. Exploitable via DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id}. Mitigation: upgrade to 0.1.9 or later.
Original description
The description as published by the source.
Platform members can delete owner issue dependencies through member-owned related issues
Summary
praisonai-platform 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.
Technical Details
The affected boundary is the difference between ordinary workspace membership and owner/admin authority over destructive changes to owner-created issue workflow state. src/praisonai-platform/praisonai_platform/api/routes/dependencies.py defines DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id}. The route first verifies that the URL issue_id is in the workspace, loads the dependency by dep_id, and accepts the dependency when either dep.issue_id == issue_id or dep.depends_on_issue_id == issue_id. It then calls require_delete_permission(workspace_id, user, session, resource_owner_id=issue.creator_id) for the URL issue only.
src/praisonai-platform/praisonai_platform/api/deps.py implements require_delete_permission as "admin/owner or resource owner". That helper is appropriate when the protected resource has a single owner, but the dependency route lets the caller choose either side of the relationship before the helper runs. I…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-62179 has been found in praisonai-platform.
Attackers can target a specific entry point like DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id} over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade praisonai-platform to 0.1.9 or later.
If unsure, ask your IT team or search "praisonai-platform CVE-2026-62179" on the vendor's site.
CVE-2026-62179 (praisonai-platform) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id} / POST /workspaces/{workspace_id}/issues/{issue_id}/dependencies/ / issue_id / dep_id
Patched: 0.1.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in praisonai-platform. Attackers reach the vulnerable code path via DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id}.
Check the vendor advisory for the affected versions of praisonai-platform. Attack surface: DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id} / POST /workspaces/{workspace_id}/issues/{issue_id}/dependencies/ / issue_id / dep_id.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 0.1.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id} requests with malformed payloads or SQL meta-characters. Run grep -r 'praisonai-platform' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'praisonai-platform' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
praisonai-platformを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade praisonai-platform to 0.1.9ステージング環境で 0.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against DELETE /workspaces/{workspace_id}/issues/{issue_id}/dependencies/{dep_id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。