praisonai-platform: Any workspace member can add arbitrary user as owner via POST /workspaces/{id}/members
CVE-2026-47413GHSA-8g2p-pqm3-fcfh
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai-platform 0.1.4), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI praisonai-platform
- Affected
- < 0.1.4
- Fixed in
- 0.1.4
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-8g2p-pqm3-fcfh lists affected ranges: PyPI praisonai-platform >=0 <0.1.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-8g2p-pqm3-fcfh lists affected ranges: PyPI praisonai-platform >=0 <0.1.4 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
- EPSS
- CVE-2026-47413: 0.26% estimated exploitation activity in the next 30 days; percentile 18.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Type: Privilege escalation / cross-tenant member injection. The POST /workspaces/{workspaceid}/members endpoint is gated only by requireworkspacemember(workspaceid) (default minrole="member") and forwards the request body's userid and role straight into MemberService.add(workspaceid, userid, role), which has no caller-permission check. A user with the lowest workspace privilege can add any user (including a new attacker-controlled second account, or an existing account they want to grief) as owner of the workspace. File: src/praisonai-platform/praisonaiplatform/api/routes/workspaces.py, lines 92-101; services/memberservice.py, lines 26-38. Root cause: MemberService.add validates only that role is in VALIDROLES = {"owner", "admin", "member"} — the value, not the caller's right to assign it. The route's Depends(requireworkspacemember) resolves to the default minrole="member". So a member-level token plus one POST gives the attacker an alternate identity with owner role inside…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-8g2p-pqm3-fcfh
- Revision 2 · amended ·
Amended from osv record GHSA-8g2p-pqm3-fcfh
- Revision 1 · created ·
Published from ghsa record GHSA-8g2p-pqm3-fcfh
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-47413
Advisory: praisonai-platform: Any workspace member can add arbitrary user as owner via POST /workspaces/{id}/members
IDs: CVE-2026-47413, GHSA-8g2p-pqm3-fcfh
Record: https://patchnext.com/advisories/cve-2026-47413 (revision 3, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai-platform 0.1.4. A vendor fix does not mean a deployment is fixed.
## Affected components
- PyPI praisonai-platform: affected < 0.1.4; fixed in 0.1.4
## Suggested inspection (read-only)
- `python -m pip show praisonai-platform`: prints the installed version. Run with the environment that serves production active.
## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.
## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonai-platform.
- Repeat the inspection and confirm that only fixed versions remain installed.
## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.
## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.
## Sources
- Verified: https://github.com/advisories/GHSA-8g2p-pqm3-fcfh (GitHub-reviewed advisory GHSA-8g2p-pqm3-fcfh lists affected ranges: PyPI praisonai-platform >=0 <0.1.4)
- Verified: https://osv.dev/vulnerability/GHSA-8g2p-pqm3-fcfh (OSV record GHSA-8g2p-pqm3-fcfh lists affected ranges: PyPI praisonai-platform >=0 <0.1.4 (fixed))
Commands are suggestions: review each one before running it.Loading voting…