Privilege Escalation in praisonai-platform (CVE-2026-47416)
Summary
Vulnerability in praisonai-platform (CVE-2026-47416). Confidential information can be exposed externally. Exploitable via PATCH /workspaces/{workspace_id}/members/{user_id}. Mitigation: upgrade to 0.1.4 or later.
Original description
The description as published by the source.
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 are vulnerable to vertical privilege escalation. The PATCH /workspaces/{workspace_id}/members/{user_id} endpoint is gated by require_workspace_member(workspace_id), which defaults to min_role="member" and is never overridden by the route. The handler then calls MemberService.update_role(workspace_id, user_id, body.role) which sets the target member's role to whatever the request body specifies, with no check that the caller has owner-or-admin privilege, no check that the new role is not higher than the caller's own, and no check that the caller is not silently promoting themselves. PraisonAI Platform version 0.1.4 patches 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-47416 has been found in praisonai-platform.
Attackers can target a specific entry point like PATCH /workspaces/{workspace_id}/members/{user_id} over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.6/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-47416" on the vendor's site.
CVE-2026-47416 (praisonai-platform) — CWE-269 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /workspaces/{workspace_id}/members/{user_id} / PATCH /workspaces/W/members/ / GET /auth/me / 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-269) exists in praisonai-platform. Attackers reach the vulnerable code path via PATCH /workspaces/{workspace_id}/members/{user_id}.
Check the vendor advisory for the affected versions of praisonai-platform. Attack surface: PATCH /workspaces/{workspace_id}/members/{user_id} / PATCH /workspaces/W/members/ / GET /auth/me / require_workspace_member.
Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.
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 PATCH /workspaces/{workspace_id}/members/{user_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 'PATCH /workspaces/{workspace_id}/members/{user_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /workspaces/{workspace_id}/members/{user_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 PATCH /workspaces/{workspace_id}/members/{user_id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com