praisonai-platform: list_issue_activity returns activity log for any issue regardless of workspace ownership
CVE-2026-47408GHSA-27p4-pjqv-whgj
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-27p4-pjqv-whgj 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-27p4-pjqv-whgj 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
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-47408: 0.29% estimated exploitation activity in the next 30 days; percentile 21.99 (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: Insecure Direct Object Reference. The GET /workspaces/{workspaceid}/issues/{issueid}/activity endpoint is gated by requireworkspacemember(workspaceid) and dispatches to ActivityService.listforissue(issueid), which executes SELECT FROM activity WHERE issueid = :issueid with no workspace constraint. A user who is a member of any workspace can read the full activity log of any issue across the entire multi-tenant deployment. File: src/praisonai-platform/praisonaiplatform/api/routes/activity.py, lines 32-43; services/activityservice.py's listforissue method. Root cause: the route extracts workspaceid from the URL path, uses it solely for the membership gate, then passes the URL-supplied issueid directly to ActivityService.listforissue(issueid) without verifying which workspace the issue belongs to. The companion listworkspaceactivity endpoint at line 19-29 is implemented correctly (it passes workspaceid to svc.listforworkspace(workspaceid)) — the asymmetry is the smoking…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-27p4-pjqv-whgj
- Revision 1 · created ·
Published from osv record GHSA-27p4-pjqv-whgj
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-47408 Advisory: praisonai-platform: list_issue_activity returns activity log for any issue regardless of workspace ownership IDs: CVE-2026-47408, GHSA-27p4-pjqv-whgj Record: https://patchnext.com/advisories/cve-2026-47408 (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: Medium (CVSS 6.5) 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-27p4-pjqv-whgj (OSV record GHSA-27p4-pjqv-whgj lists affected ranges: PyPI praisonai-platform >=0 <0.1.4 (fixed)) - Verified: https://github.com/advisories/GHSA-27p4-pjqv-whgj (GitHub-reviewed advisory GHSA-27p4-pjqv-whgj lists affected ranges: PyPI praisonai-platform >=0 <=0.1.2) Commands are suggestions: review each one before running it.
Loading voting…