Vulnerability in praisonai-platform (CVE-2026-48169)
Summary
Vulnerability in praisonai-platform (CVE-2026-48169). Successful exploitation can lead to full system takeover. Exploitable via GET /api/v1/workspaces/{workspace_id}/issues/{issue_id}. Mitigation: upgrade to 0.1.4 or later.
Original description
The description as published by the source.
PraisonAI is a multi-agent teams system. Versions prior to 0.1.4 of the PraisonAI Platform API have two authorization failures that together break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, so any authenticated user can read, modify, and delete resources in any workspace just by swapping UUIDs in their API requests. On top of that, every member management endpoint (add, update role, remove) only requires min_role="member", which lets any workspace member promote themselves to owner and kick out the original owner. A low-privilege member of one workspace can steal data from every other workspace and take over any workspace they belong to. Both issues come from the same gap: the route layer pulls workspace_id from the URL and verifies membership, but the service layer ignores the workspace scope for resource lookups and ignores the caller's role level for member operations. The require_workspace_member() dependency does its job correctly. The problem is that the service layer doesn't use the information it provides. Version 0.1.4 of the PraisonAI Platform API patch the issue.
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-48169 has been found in praisonai-platform.
Attackers can target a specific entry point like GET /api/v1/workspaces/{workspace_id}/issues/{issue_id} over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade praisonai-platform to 0.1.4 or later.
If unsure, ask your IT team or search "praisonai-platform CVE-2026-48169" on the vendor's site.
CVE-2026-48169 (praisonai-platform) — CWE-639 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/workspaces/{workspace_id}/issues/{issue_id} / workspace_id / project_id / require_workspace_member
Patched: 0.1.4 — 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-639) exists in praisonai-platform. Attackers reach the vulnerable code path via GET /api/v1/workspaces/{workspace_id}/issues/{issue_id}.
Check the vendor advisory for the affected versions of praisonai-platform. Attack surface: GET /api/v1/workspaces/{workspace_id}/issues/{issue_id} / workspace_id / project_id / require_workspace_member.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 0.1.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/workspaces/{workspace_id}/issues/{issue_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 'GET /api/v1/workspaces/{workspace_id}/issues/{issue_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/workspaces/{workspace_id}/issues/{issue_id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade praisonai-platform to 0.1.4ステージング環境で 0.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/workspaces/{workspace_id}/issues/{issue_id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- web github.com