praisonai-platform: Missing authorization on member removal enables full workspace takeover by any user regardless of role
CVE-2026-47409GHSA-w388-2392-px73
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.2
- Fixed in
- 0.1.4
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-w388-2392-px73 lists affected ranges: PyPI praisonai-platform >=0 <0.1.4 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-w388-2392-px73 lists affected ranges: PyPI praisonai-platform >=0 <=0.1.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- EPSS
- CVE-2026-47409: 0.34% estimated exploitation activity in the next 30 days; percentile 28.16 (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: Authorization bypass enabling owner lockout. The DELETE /workspaces/{workspaceid}/members/{userid} endpoint is gated only by requireworkspacemember(workspaceid) (default minrole="member"). Any member can remove any other member, including the workspace owner, using a single DELETE. There is no caller-role check, no target-role check, no "cannot remove last owner" guard. File: src/praisonai-platform/praisonaiplatform/api/routes/workspaces.py, lines 130-140; services/memberservice.py, lines 71-78. Root cause: MemberService.remove(workspaceid, userid) performs the deletion without any caller-permission check or owner-protection logic. The route accepts the URL-supplied userid and dispatches it straight through. The role hierarchy (MemberService.hasrole) is implemented but never invoked here. A member-tier attacker can issue DELETE .../members/<owneruserid and immediately lock the legitimate owner out of the workspace. Affected Code File 1:…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-w388-2392-px73
- Revision 1 · created ·
Published from osv record GHSA-w388-2392-px73
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-47409 Advisory: praisonai-platform: Missing authorization on member removal enables full workspace takeover by any user regardless of role IDs: CVE-2026-47409, GHSA-w388-2392-px73 Record: https://patchnext.com/advisories/cve-2026-47409 (revision 2, 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: High (CVSS 8.1) 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.2; 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://osv.dev/vulnerability/GHSA-w388-2392-px73 (OSV record GHSA-w388-2392-px73 lists affected ranges: PyPI praisonai-platform >=0 <0.1.4 (fixed)) - Verified: https://github.com/advisories/GHSA-w388-2392-px73 (GitHub-reviewed advisory GHSA-w388-2392-px73 lists affected ranges: PyPI praisonai-platform >=0 <=0.1.2) Commands are suggestions: review each one before running it.
Loading voting…