PraisonAI: Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass
# Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass ## Summary `praisonai-platform` lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch `lead_id` to their own user id and then delete the owner-created project, bypassing a delete guard that correctly returned `403` before the reassignment. ## Technical Details The affected boundary is the difference between "is a workspace member" and "owns or administers this resource". `src/praisonai-platform/praisonai_platform/api/deps.py` defines `require_workspace_member`, `require_workspace_admin`, `require_workspace_owner`, and `require_delete_permission`. `require_workspace_member` only checks that the caller has at least the `member` role in the workspace, while `require_delete_permission` allows delete only for workspace admins/owners or the resource owner. The project update route in `src/praisonai-platform/praisonai_platform/api/routes/projects.py` defines `PATCH /workspaces/{workspace_id}/projects/{project_id}` with `user: AuthIdentity = Depends(require_workspace_member)`. It passes `title`, `description`, `status`, `lead_type`, and `lead_id` into `ProjectService.update`. `src/praisonai-platform/praisonai_platform/services/project_service.py` then writes `project.lead_id = lead_id` when supplied. The paired project delete route firs
- Products
- praisonai-platform
- Affected versions
- 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.6, 0.1.8
- Fixed versions
- 0.1.9
- CVEs
- CVE-2026-61442
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 18:17 UTC · Revision 1
Source evidence
PraisonAI: Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass
core-osv · Original sourcePublished 8 Oct 2026, 22:01 UTC
# Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass ## Summary `praisonai-platform` lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch `lead_id` to their own user id and then delete the owner-created project, bypassing a delete guard that correctly returned `403` before the reassignment. ## Technical Details The affected boundary is the difference between "is a workspace member" and "owns or administers this resource". `src/praisonai-platform/praisonai_platform/api/deps.py` defines `require_workspace_member`, `require_workspace_admin`, `require_workspace_owner`, and `require_delete_permission`. `require_workspace_member` only checks that the caller has at least the `member` role in the workspace, while `require_delete_permission` allows delete only for workspace admins/owners or the resource owner. The project update route in `src/praisonai-platform/praisonai_platform/api/routes/projects.py` defines `PATCH /workspaces/{workspace_id}/projects/{project_id}` with `user: AuthIdentity = Depends(require_workspace_member)`. It passes `title`, `description`, `status`, `lead_type`, and `lead_id` into `ProjectService.update`. `src/praisonai-platform/praisonai_platform/services/project_service.py` then writes `project.lead_id = lead_id` when supplied. The paired project delete route firs
osv:GHSA-c78w-2q4r-68r7
praisonai-platform
Fixed versions: 0.1.9
Complete source record
{
"id": "cfec30c7b78741ff42caf89c1413ecfccd79111414e08d702bbf0d05a7cb9dc3",
"url": "https://osv.dev/vulnerability/GHSA-c78w-2q4r-68r7",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "PraisonAI: Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass",
"summary": "# Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass ## Summary `praisonai-platform` lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch `lead_id` to their own user id and then delete the owner-created project, bypassing a delete guard that correctly returned `403` before the reassignment. ## Technical Details The affected boundary is the difference between \"is a workspace member\" and \"owns or administers this resource\". `src/praisonai-platform/praisonai_platform/api/deps.py` defines `require_workspace_member`, `require_workspace_admin`, `require_workspace_owner`, and `require_delete_permission`. `require_workspace_member` only checks that the caller has at least the `member` role in the workspace, while `require_delete_permission` allows delete only for workspace admins/owners or the resource owner. The project update route in `src/praisonai-platform/praisonai_platform/api/routes/projects.py` defines `PATCH /workspaces/{workspace_id}/projects/{project_id}` with `user: AuthIdentity = Depends(require_workspace_member)`. It passes `title`, `description`, `status`, `lead_type`, and `lead_id` into `ProjectService.update`. `src/praisonai-platform/praisonai_platform/services/project_service.py` then writes `project.lead_id = lead_id` when supplied. The paired project delete route firs",
"evidence": "osv:GHSA-c78w-2q4r-68r7",
"products": [
{
"name": {
"value": "praisonai-platform",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "0.1.9",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "0.1.0",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.1",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.2",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.3",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.4",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.6",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.8",
"evidence": "/affected/0/versions"
}
]
}
],
"severity": "high",
"structured": {
"id": "GHSA-c78w-2q4r-68r7",
"aliases": [
"CVE-2026-61442",
"GHSA-c78w-2q4r-68r7",
"PYSEC-2026-4262"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "0.1.9"
}
]
}
],
"package": {
"name": "praisonai-platform",
"purl": "pkg:pypi/praisonai-platform",
"ecosystem": "PyPI"
},
"versions": [
"0.1.0",
"0.1.1",
"0.1.2",
"0.1.3",
"0.1.4",
"0.1.6",
"0.1.8"
],
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-c78w-2q4r-68r7/GHSA-c78w-2q4r-68r7.json",
"last_known_affected_version_range": "<= 0.1.8"
}
}
],
"modified": "2026-10-15T14:56:22.070528327Z",
"provider": "osv",
"references": [
"https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-c78w-2q4r-68r7",
"https://nvd.nist.gov/vuln/detail/CVE-2026-61442",
"https://github.com/MervinPraison/PraisonAI/commit/846568c7a5d8ce9e71e56e4c213f027c04909753",
"https://github.com/MervinPraison/PraisonAI",
"https://www.vulncheck.com/advisories/praisonai-platform-before-authorization-bypass-via-patch"
],
"provider_metadata": {
"cwe_ids": [
"CWE-862",
"CWE-863"
],
"severity": "HIGH",
"github_reviewed": true,
"nvd_published_at": null,
"github_reviewed_at": "2026-10-08T22:01:11Z"
}
},
"related_cves": [
{
"value": "CVE-2026-61442",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 332696,
"published_at": "2026-10-08T22:01:11+00:00"
}PraisonAI: Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass
core-osv · Original sourcePublished 15 Oct 2026, 10:22 UTC
# Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass ## Summary `praisonai-platform` lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch `lead_id` to their own user id and then delete the owner-created project, bypassing a delete guard that correctly returned `403` before the reassignment. ## Technical Details The affected boundary is the difference between "is a workspace member" and "owns or administers this resource". `src/praisonai-platform/praisonai_platform/api/deps.py` defines `require_workspace_member`, `require_workspace_admin`, `require_workspace_owner`, and `require_delete_permission`. `require_workspace_member` only checks that the caller has at least the `member` role in the workspace, while `require_delete_permission` allows delete only for workspace admins/owners or the resource owner. The project update route in `src/praisonai-platform/praisonai_platform/api/routes/projects.py` defines `PATCH /workspaces/{workspace_id}/projects/{project_id}` with `user: AuthIdentity = Depends(require_workspace_member)`. It passes `title`, `description`, `status`, `lead_type`, and `lead_id` into `ProjectService.update`. `src/praisonai-platform/praisonai_platform/services/project_service.py` then writes `project.lead_id = lead_id` when supplied. The paired project delete route firs
osv:PYSEC-2026-4262
praisonai-platform
Fixed versions: 0.1.9
Complete source record
{
"id": "a397c4b34a24e7f016557da7b016342bb2c701d806ebd07470a37a32fbbfe0b0",
"url": "https://osv.dev/vulnerability/PYSEC-2026-4262",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "PraisonAI: Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass",
"summary": "# Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass ## Summary `praisonai-platform` lets an ordinary workspace member patch owner-created project, issue, and agent records even though the paired delete routes enforce owner/admin authorization. For projects, the member can first patch `lead_id` to their own user id and then delete the owner-created project, bypassing a delete guard that correctly returned `403` before the reassignment. ## Technical Details The affected boundary is the difference between \"is a workspace member\" and \"owns or administers this resource\". `src/praisonai-platform/praisonai_platform/api/deps.py` defines `require_workspace_member`, `require_workspace_admin`, `require_workspace_owner`, and `require_delete_permission`. `require_workspace_member` only checks that the caller has at least the `member` role in the workspace, while `require_delete_permission` allows delete only for workspace admins/owners or the resource owner. The project update route in `src/praisonai-platform/praisonai_platform/api/routes/projects.py` defines `PATCH /workspaces/{workspace_id}/projects/{project_id}` with `user: AuthIdentity = Depends(require_workspace_member)`. It passes `title`, `description`, `status`, `lead_type`, and `lead_id` into `ProjectService.update`. `src/praisonai-platform/praisonai_platform/services/project_service.py` then writes `project.lead_id = lead_id` when supplied. The paired project delete route firs",
"evidence": "osv:PYSEC-2026-4262",
"products": [
{
"name": {
"value": "praisonai-platform",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "0.1.9",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "0.1.0",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.1",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.2",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.3",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.4",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.6",
"evidence": "/affected/0/versions"
},
{
"value": "0.1.8",
"evidence": "/affected/0/versions"
}
]
}
],
"severity": "high",
"structured": {
"id": "PYSEC-2026-4262",
"aliases": [
"CVE-2026-61442",
"GHSA-c78w-2q4r-68r7",
"PYSEC-2026-4262"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "0.1.9"
}
]
}
],
"package": {
"name": "praisonai-platform",
"purl": "pkg:pypi/praisonai-platform",
"ecosystem": "PyPI"
},
"versions": [
"0.1.0",
"0.1.1",
"0.1.2",
"0.1.3",
"0.1.4",
"0.1.6",
"0.1.8"
],
"database_specific": {
"source": "https://github.com/pypa/advisory-database/blob/main/vulns/praisonai-platform/PYSEC-2026-4262.yaml"
}
}
],
"modified": "2026-10-15T14:45:11.730754105Z",
"provider": "osv",
"references": [
"https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-c78w-2q4r-68r7",
"https://nvd.nist.gov/vuln/detail/CVE-2026-61442",
"https://github.com/MervinPraison/PraisonAI/commit/846568c7a5d8ce9e71e56e4c213f027c04909753",
"https://github.com/MervinPraison/PraisonAI",
"https://www.vulncheck.com/advisories/praisonai-platform-before-authorization-bypass-via-patch",
"https://pypi.org/project/praisonai-platform",
"https://github.com/advisories/GHSA-c78w-2q4r-68r7"
]
},
"related_cves": [
{
"value": "CVE-2026-61442",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 332654,
"published_at": "2026-10-15T10:22:53.695362+00:00"
}