CVE-2026-47406: praisonai-platform IDOR Vulnerability

HIGH
Advisory Identifier: GHSA-4x6r-9v57-3gqw
CVSS 8.1
CWE-639
Published
Advisory Summary

CVE-2026-47406 is a HIGH (CVSS 8.1) idor vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting praisonai-platform libraries in the PyPI ecosystem. The issue involves idor in dependency endpoints allows cross-workspace issue linking, reading, and deletion due to missing ownership checks. Remediation is available by upgrading affected packages to version 0.1.4.

CVE-2026-47406 at a Glance

CVE Identifier CVE-2026-47406
GHSA Identifier GHSA-4x6r-9v57-3gqw
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product praisonai-platform
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-47406

To remediate this vulnerability, upgrade all affected praisonai-platform dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

praisonai-platform fixed: 0.1.4
pip install praisonai-platform>=0.1.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show praisonai-platform

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-47406, inspect your installed packages using pip:

pip show praisonai-platform

Analyze the terminal output to locate any version of praisonai-platform in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.1.4), your application is affected.

Note: The pip show praisonai-platform command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In praisonai-platform, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary **Type:** Insecure Direct Object Reference. The dependency endpoints (`POST/GET /workspaces/{workspace_id}/issues/{issue_id}/dependencies` and `DELETE .../dependencies/{dep_id}`) gate access on `require_workspace_member(workspace_id)` only, then dispatch to `DependencyService` calls that take URL/body-supplied issue and dependency IDs without verifying any of them belong to the membership-checked workspace. Most damaging: `create_dependency` accepts `body.depends_on_issue_id` from the request body — that ID is checked against nothing — letting an attacker create a "blocks" or "related" link between any two issues anywhere in the database. **File:** `src/praisonai-platform/praisonai_platform/api/routes/dependencies.py`, lines 22-58; `services/dependency_service.py`, lines 26-65. **Root cause:** the same `Depends(require_workspace_member)` default-min-role pattern as the companion IDORs, plus a service layer (`DependencyService`) where every method takes raw IDs and queries them directly. `create(issue_id, depends_on_issue_id, ...)` writes a row with no workspace verification on either ID. `list_for_issue(issue_id)` returns dependencies in either direction. `delete(dep_id)` is a primary-key delete with no workspace predicate. ## Affected Code **File 1:** `src/praisonai-platform/praisonai_platform/api/routes/dependencies.py`, lines 22-58. ```python @router.post("/", response_model=DependencyResponse, status_code=status.HTTP_201_CREATED) async def create_dependency( workspace_id: str, issue_id: str, body: DependencyCreate, user: AuthIdentity = Depends(require_workspace_member), session: AsyncSession = Depends(get_db), ): svc = DependencyService(session) dep = await svc.create(issue_id, body.depends_on_issue_id, body.type) # <-- BUG: neither id is workspace-checked return DependencyResponse.model_validate(dep) @router.get("/", response_model=List[DependencyResponse]) async def list_dependencies( workspace_id: str, issue_id: str, user: AuthIdentity = Depends(require_workspace_member), session: AsyncSession = Depends(get_db), ): svc = DependencyService(session) deps = await svc.list_for_issue(issue_id) # <-- BUG: returns dependencies for any issue return [DependencyResponse.model_validate(d) for d in deps] @router.delete("/{dep_id}", status_code=status.HTTP_204_NO_CONTENT) async def delete_dependency( workspace_id: str, issue_id: str, dep_id: str, user: AuthIdentity = Depends(require_workspace_member), session: AsyncSession = Depends(get_db), ): svc = DependencyService(session) deleted = await svc.delete(dep_id) # <-- BUG: deletes any dependency by id if not deleted: raise HTTPException(status_code=404, detail="Dependency not found") ``` **File 2:** `src/praisonai-platform/praisonai_platform/services/dependency_service.py`, lines 26-65. ```python async def create(self, issue_id: str, depends_on_issue_id: str, dep_type: str = "blocks") -> IssueDependency: if dep_type not in VALID_TYPES: raise ValueError(...) dep = IssueDependency( issue_id=issue_id, # <-- accepts any depends_on_issue_id=depends_on_issue_id, # <-- accepts any (from request body) type=dep_type, ) self._session.add(dep); await self._session.flush(); return dep async def list_for_issue(self, issue_id: str) -> list[IssueDependency]: stmt = select(IssueDependency).where( (IssueDependency.issue_id == issue_id) | (IssueDependency.depends_on_issue_id == issue_id) ) return list((await self._session.execute(stmt)).scalars().all()) async def delete(self, dep_id: str) -> bool: dep = await self.get(dep_id) # session.get(IssueDependency, dep_id) — no workspace check ... ``` **Why it's wrong:** the request-body `depends_on_issue_id` is the worst part: an attacker can link any two issues across any two workspaces, polluting both workspaces' dependency graphs with attacker-chosen relationships ("blocks", "blocked_by", "related"). The triagers in the foreign workspace see their issue suddenly blocked by an unrelated foreign issue, breaking sprint planning and creating false correlation. The `delete(dep_id)` path lets an attacker remove legitimate cross-issue links between any two foreign workspaces, also disrupting their planning. The `list_for_issue` path leaks the dependency graph for any issue in the deployment. ## Exploit Chain 1. Attacker is a member of workspace `W_attacker` and harvests two foreign-workspace issue UUIDs `I1` (in `W_target1`) and `I2` (in `W_target2`). They leak via the activity feed, comment threads, error messages, exported dumps, the agent prompt history, or any other channel that ever serialises an issue ID. State: attacker holds two foreign issue UUIDs. 2. Attacker sends `POST /workspaces/W_attacker/issues/I1/dependencies` with `Authorization: Bearer <attacker_jwt>` and body `{"depends_on_issue_id": "I2", "type": "blocks"}`. State: control flow enters `create_dependency` with `issue_id=I1` (foreign), `depends_on_issue_id=I2` (foreign). 3. `require_workspace_member(W_attacker, attacker)` passes (attacker is a member of `W_attacker`). `DependencyService.create(I1, I2, "blocks")` writes a new row `IssueDependency(issue_id=I1, depends_on_issue_id=I2, type="blocks")`. State: there is now a cross-workspace dependency between two foreign issues, written by the attacker. 4. The triage UIs of `W_target1` and `W_target2` now show that the foreign issue is blocked by an unrelated issue in another workspace. Workflow rules that key off "cannot close while blocked" will refuse to let the legitimate triagers close `I1`. State: foreign workflow disrupted. 5. Attacker repeats with `GET /workspaces/W_attacker/issues/I1/dependencies` to read the dependency graph for any foreign issue (information disclosure, project relationship mapping), or with `DELETE .../{dep_id}` (after enumerating dep_ids via the list call) to strip legitimate dependencies between foreign issues, breaking blocked-by chains. 6. Final state: with one workspace-member token, the attacker reads, writes, and deletes dependencies on every issue in the multi-tenant deployment, polluting the dependency graphs of foreign workspaces. ## Security Impact **Severity:** sec-high. CVSS 7.6: network attack, low complexity, low privileges, no user interaction, scope unchanged, high confidentiality (cross-workspace dependency graph disclosure), high integrity (cross-workspace dependency injection and deletion), no availability claim (workflow disruption is integrity, not availability). **Attacker capability:** read any issue's dependency graph; create arbitrary "blocks" / "blocked_by" / "related" links between any two issues across any two workspaces; delete any dependency by id. The most surprising primitive is the cross-workspace LINKING — the only one of the IDORs in this codebase where a single attacker request can affect TWO foreign workspaces at once. **Preconditions:** `praisonai-platform` is deployed multi-tenant; attacker has any membership token; foreign issue UUIDs are reachable. **Differential:** source-inspection-verified end-to-end. The asymmetry between this service (no workspace predicate anywhere) and `MemberService.get(workspace_id, user_id)` (correctly composite-keyed) confirms the gap. With the suggested fix below, the route would resolve both the URL `issue_id` and the body `depends_on_issue_id` against `IssueService.get(workspace_id, ...)` before allowing the dependency to be written. ## Suggested Fix Resolve every issue id (URL and body) against `workspace_id` at the route layer before dispatching. The route helper from the issue-IDOR companion advisory can be reused. ```diff --- a/src/praisonai-platform/praisonai_platform/api/routes/dependencies.py +++ b/src/praisonai-platform/praisonai_platform/api/routes/dependencies.py @@ -22,11 +22,16 @@ @router.post("/", response_model=DependencyResponse, status_code=status.HTTP_201_CREATED) async def create_dependency( workspace_id: str, issue_id: str, body: DependencyCreate, user: AuthIdentity = Depends(require_workspace_member), session: AsyncSession = Depends(get_db), ): + issue_svc = IssueService(session) + if await issue_svc.get(workspace_id, issue_id) is None: + raise HTTPException(status_code=404, detail="Issue not found") + if await issue_svc.get(workspace_id, body.depends_on_issue_id) is None: + raise HTTPException(status_code=404, detail="depends_on_issue_id not found in this workspace") svc = DependencyService(session) dep = await svc.create(issue_id, body.depends_on_issue_id, body.type) return DependencyResponse.model_validate(dep) ``` Apply the same `issue_svc.get(workspace_id, issue_id)` precondition to `list_dependencies` and `delete_dependency` (verifying both the issue and the dependency belong to `workspace_id`).

CVE-2026-47406 Affected praisonai-platform Versions

1 component(s)
Fixed Versions:
0.1.4
Product / Package Ecosystem Affected Versions Fixed Version
praisonai-platform
PyPI
< 0.1.4
0.1.4

References

Frequently Asked Questions

What is CVE-2026-47406?
CVE-2026-47406 is a security vulnerability in praisonai-platform involving IDOR in dependency endpoints allows cross-workspace issue linking, reading, and deletion due to missing ownership checks under CWE-639: Authorization Bypass Through User-Controlled Key.
Which praisonai-platform versions are affected?
Affected versions include releases prior to 0.1.4 across affected packages: praisonai-platform.
What version fixes CVE-2026-47406?
Upgrading to 0.1.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is praisonai-platform affected?
Yes, praisonai-platform is affected in releases prior to 0.1.4. Upgrade your dependency to 0.1.4 or later.
What is the CVSS score of CVE-2026-47406?
CVE-2026-47406 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-47406?
CVE-2026-47406 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check PyPI dependencies for CVE-2026-47406?
Run the dependency tree command: 'pip show praisonai-platform'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4x6r-9v57-3gqw",
  "modified" : "2026-05-29T22:45:48Z",
  "published" : "2026-05-29T22:45:48Z",
  "aliases" : [ "CVE-2026-47406" ],
  "summary" : "praisonai-platform: IDOR in dependency endpoints allows cross-workspace issue linking, reading, and deletion due to missing ownership checks",
  "details" : "## Summary\n\n**Type:** Insecure Direct Object Reference. The dependency endpoints (`POST/GET /workspaces/{workspace_id}/issues/{issue_id}/dependencies` and `DELETE .../dependencies/{dep_id}`) gate access on `require_workspace_member(workspace_id)` only, then dispatch to `DependencyService` calls that take URL/body-supplied issue and dependency IDs without verifying any of them belong to the membership-checked workspace. Most damaging: `create_dependency` accepts `body.depends_on_issue_id` from the request body — that ID is checked against nothing — letting an attacker create a \"blocks\" or \"related\" link between any two issues anywhere in the database.\n**File:** `src/praisonai-platform/praisonai_platform/api/routes/dependencies.py`, lines 22-58; `services/dependency_service.py`, lines 26-65.\n**Root cause:** the same `Depends(require_workspace_member)` default-min-role pattern as the companion IDORs, plus a service layer (`DependencyService`) where every method takes raw IDs and queries them directly. `create(issue_id, depends_on_issue_id, ...)` writes a row with no workspace verification on either ID. `list_for_issue(issue_id)` returns dependencies in either direction. `delete(dep_id)` is a primary-key delete with no workspace predicate.\n\n## Affected Code\n\n**File 1:** `src/praisonai-platform/praisonai_platform/api/routes/dependencies.py`, lines 22-58.\n\n```python\n@router.post(\"/\", response_model=DependencyResponse, status_code=status.HTTP_201_CREATED)\nasync def create_dependency(\n    workspace_id: str,\n    issue_id: str,\n    body: DependencyCreate,\n    user: AuthIdentity = Depends(require_workspace_member),\n    session: AsyncSession = Depends(get_db),\n):\n    svc = DependencyService(session)\n    dep = await svc.create(issue_id, body.depends_on_issue_id, body.type)  # <-- BUG: neither id is workspace-checked\n    return DependencyResponse.model_validate(dep)\n\n\n@router.get(\"/\", response_model=List[DependencyResponse])\nasync def list_dependencies(\n    workspace_id: str,\n    issue_id: str,\n    user: AuthIdentity = Depends(require_workspace_member),\n    session: AsyncSession = Depends(get_db),\n):\n    svc = DependencyService(session)\n    deps = await svc.list_for_issue(issue_id)                              # <-- BUG: returns dependencies for any issue\n    return [DependencyResponse.model_validate(d) for d in deps]\n\n\n@router.delete(\"/{dep_id}\", status_code=status.HTTP_204_NO_CONTENT)\nasync def delete_dependency(\n    workspace_id: str,\n    issue_id: str,\n    dep_id: str,\n    user: AuthIdentity = Depends(require_workspace_member),\n    session: AsyncSession = Depends(get_db),\n):\n    svc = DependencyService(session)\n    deleted = await svc.delete(dep_id)                                     # <-- BUG: deletes any dependency by id\n    if not deleted:\n        raise HTTPException(status_code=404, detail=\"Dependency not found\")\n```\n\n**File 2:** `src/praisonai-platform/praisonai_platform/services/dependency_service.py`, lines 26-65.\n\n```python\nasync def create(self, issue_id: str, depends_on_issue_id: str, dep_type: str = \"blocks\") -> IssueDependency:\n    if dep_type not in VALID_TYPES:\n        raise ValueError(...)\n    dep = IssueDependency(\n        issue_id=issue_id,                                              # <-- accepts any\n        depends_on_issue_id=depends_on_issue_id,                        # <-- accepts any (from request body)\n        type=dep_type,\n    )\n    self._session.add(dep); await self._session.flush(); return dep\n\nasync def list_for_issue(self, issue_id: str) -> list[IssueDependency]:\n    stmt = select(IssueDependency).where(\n        (IssueDependency.issue_id == issue_id) | (IssueDependency.depends_on_issue_id == issue_id)\n    )\n    return list((await self._session.execute(stmt)).scalars().all())\n\nasync def delete(self, dep_id: str) -> bool:\n    dep = await self.get(dep_id)                                        # session.get(IssueDependency, dep_id) — no workspace check\n    ...\n```\n\n**Why it's wrong:** the request-body `depends_on_issue_id` is the worst part: an attacker can link any two issues across any two workspaces, polluting both workspaces' dependency graphs with attacker-chosen relationships (\"blocks\", \"blocked_by\", \"related\"). The triagers in the foreign workspace see their issue suddenly blocked by an unrelated foreign issue, breaking sprint planning and creating false correlation. The `delete(dep_id)` path lets an attacker remove legitimate cross-issue links between any two foreign workspaces, also disrupting their planning. The `list_for_issue` path leaks the dependency graph for any issue in the deployment.\n\n## Exploit Chain\n\n1. Attacker is a member of workspace `W_attacker` and harvests two foreign-workspace issue UUIDs `I1` (in `W_target1`) and `I2` (in `W_target2`). They leak via the activity feed, comment threads, error messages, exported dumps, the agent prompt history, or any other channel that ever serialises an issue ID. State: attacker holds two foreign issue UUIDs.\n2. Attacker sends `POST /workspaces/W_attacker/issues/I1/dependencies` with `Authorization: Bearer <attacker_jwt>` and body `{\"depends_on_issue_id\": \"I2\", \"type\": \"blocks\"}`. State: control flow enters `create_dependency` with `issue_id=I1` (foreign), `depends_on_issue_id=I2` (foreign).\n3. `require_workspace_member(W_attacker, attacker)` passes (attacker is a member of `W_attacker`). `DependencyService.create(I1, I2, \"blocks\")` writes a new row `IssueDependency(issue_id=I1, depends_on_issue_id=I2, type=\"blocks\")`. State: there is now a cross-workspace dependency between two foreign issues, written by the attacker.\n4. The triage UIs of `W_target1` and `W_target2` now show that the foreign issue is blocked by an unrelated issue in another workspace. Workflow rules that key off \"cannot close while blocked\" will refuse to let the legitimate triagers close `I1`. State: foreign workflow disrupted.\n5. Attacker repeats with `GET /workspaces/W_attacker/issues/I1/dependencies` to read the dependency graph for any foreign issue (information disclosure, project relationship mapping), or with `DELETE .../{dep_id}` (after enumerating dep_ids via the list call) to strip legitimate dependencies between foreign issues, breaking blocked-by chains.\n6. Final state: with one workspace-member token, the attacker reads, writes, and deletes dependencies on every issue in the multi-tenant deployment, polluting the dependency graphs of foreign workspaces.\n\n## Security Impact\n\n**Severity:** sec-high. CVSS 7.6: network attack, low complexity, low privileges, no user interaction, scope unchanged, high confidentiality (cross-workspace dependency graph disclosure), high integrity (cross-workspace dependency injection and deletion), no availability claim (workflow disruption is integrity, not availability).\n**Attacker capability:** read any issue's dependency graph; create arbitrary \"blocks\" / \"blocked_by\" / \"related\" links between any two issues across any two workspaces; delete any dependency by id. The most surprising primitive is the cross-workspace LINKING — the only one of the IDORs in this codebase where a single attacker request can affect TWO foreign workspaces at once.\n**Preconditions:** `praisonai-platform` is deployed multi-tenant; attacker has any membership token; foreign issue UUIDs are reachable.\n**Differential:** source-inspection-verified end-to-end. The asymmetry between this service (no workspace predicate anywhere) and `MemberService.get(workspace_id, user_id)` (correctly composite-keyed) confirms the gap. With the suggested fix below, the route would resolve both the URL `issue_id` and the body `depends_on_issue_id` against `IssueService.get(workspace_id, ...)` before allowing the dependency to be written.\n\n## Suggested Fix\n\nResolve every issue id (URL and body) against `workspace_id` at the route layer before dispatching. The route helper from the issue-IDOR companion advisory can be reused.\n\n```diff\n--- a/src/praisonai-platform/praisonai_platform/api/routes/dependencies.py\n+++ b/src/praisonai-platform/praisonai_platform/api/routes/dependencies.py\n@@ -22,11 +22,16 @@\n @router.post(\"/\", response_model=DependencyResponse, status_code=status.HTTP_201_CREATED)\n async def create_dependency(\n     workspace_id: str,\n     issue_id: str,\n     body: DependencyCreate,\n     user: AuthIdentity = Depends(require_workspace_member),\n     session: AsyncSession = Depends(get_db),\n ):\n+    issue_svc = IssueService(session)\n+    if await issue_svc.get(workspace_id, issue_id) is None:\n+        raise HTTPException(status_code=404, detail=\"Issue not found\")\n+    if await issue_svc.get(workspace_id, body.depends_on_issue_id) is None:\n+        raise HTTPException(status_code=404, detail=\"depends_on_issue_id not found in this workspace\")\n     svc = DependencyService(session)\n     dep = await svc.create(issue_id, body.depends_on_issue_id, body.type)\n     return DependencyResponse.model_validate(dep)\n```\n\nApply the same `issue_svc.get(workspace_id, issue_id)` precondition to `list_dependencies` and `delete_dependency` (verifying both the issue and the dependency belong to `workspace_id`).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "praisonai-platform"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.1.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.1.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4x6r-9v57-3gqw"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/MervinPraison/PraisonAI"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-29T22:45:48Z",
    "nvd_published_at" : null
  }
}