Approved changes feed: RSS · Atom

cpe:2.3:a:mervinpraison:praisonai-platform:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorMervinpraison (a8b70906-90ee-5f62-923f-8aff692108ca)
ProductPraisonai Platform (48009359-3e2a-5085-8008-e95ee15d153c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-57147 vulnerable 2026-09-16 04:33:40.609592 praisonai-platform: default JWT signing secret 'dev-secret-change-me' enables token forgery
CRITICAL (9.8)
PraisonAI is a multi-agent teams system. Prior to 0.1.6, praisonai_platform/services/auth_service.py assigns the public dev-secret-change-me value to JWT_SECRET when PLATFORM_JWT_SECRET is unset, and its production guard does not run when PLATFORM_ENV is also unset because that setting defaults to dev. A remote unauthenticated attacker can mint an HS256 token with an arbitrary sub and email, and the platform's AuthService._verify_token() and get_current_user dependency accept the forged identity for protected API routes. This vulnerability is fixed in praisonai-platform 0.1.6.
Published: 2026-09-15T10:34:16.300Z
Updated: 2026-09-17T14:18:35.600Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-57148 vulnerable 2026-09-16 04:33:40.189860 praisonai-platform 0.1.4 still boots on the hardcoded JWT secret dev-secret-change-me (default-open production guard)
CRITICAL (9.8)
PraisonAI is a multi-agent teams system. Prior to 0.1.6, praisonai_platform/services/auth_service.py falls back to the public dev-secret-change-me HS256 signing key when PLATFORM_JWT_SECRET is unset, while the startup and token-issuance guards are disabled because PLATFORM_ENV also defaults to dev. An unauthenticated attacker can sign a JWT containing an attacker-chosen sub value, and AuthService._verify_token() accepts it as an authenticated identity, enabling user or workspace-owner impersonation when a target identifier is known. This vulnerability is fixed in praisonai-platform 0.1.6.
Published: 2026-09-15T10:32:22.525Z
Updated: 2026-09-16T17:45:28.460Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-48169 vulnerable 2026-09-16 04:33:04.433435 PraisonAI has Cross-Workspace IDOR and Privilege Escalation via Platform API
HIGH (8.8)
PraisonAI is a multi-agent teams system. Versions prior to 0.1.4 of the PraisonAI Platform API have two authorization failures that together break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, so any authenticated user can read, modify, and delete resources in any workspace just by swapping UUIDs in their API requests. On top of that, every member management endpoint (add, update role, remove) only requires `min_role="member"`, which lets any workspace member promote themselves to owner and kick out the original owner. A low-privilege member of one workspace can steal data from every other workspace and take over any workspace they belong to. Both issues come from the same gap: the route layer pulls `workspace_id` from the URL and verifies membership, but the service layer ignores the workspace scope for resource lookups and ignores the caller's role level for member operations. The `require_workspace_member()` dependency does its job correctly. The problem is that the service layer doesn't use the information it provides. Version 0.1.4 of the PraisonAI Platform API patch the issue.
Published: 2026-08-07T21:22:04.197Z
Updated: 2026-08-11T01:17:51.206Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47419 vulnerable 2026-07-29 00:55:00.231999 praisonai-platform: Agent endpoints accept any agent_id without workspace ownership check, cross-workspace read/update/delete IDOR
HIGH (8.3)
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an* Insecure Direct Object Reference. The agent CRUD endpoints (`GET / PATCH / DELETE /workspaces/{workspace_id}/agents/{agent_id}`) gate access on `require_workspace_member(workspace_id)` only, then resolve `agent_id` through `AgentService.get(agent_id)` which is a primary-key lookup with no workspace constraint. A user who is a member of any workspace `W1` can read, modify, or delete agents that belong to a different workspace `W2` by guessing or harvesting an agent UUID and calling `…/workspaces/W1/agents/<W2-agent-id>`. PraisonAI Platform version 0.1.4 patches the issue.
Published: 2026-07-21T17:31:58.909Z
Updated: 2026-07-22T14:23:46.691Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47418 vulnerable 2026-07-29 00:55:00.231871 praisonai-platform: Project endpoints accept any project_id without workspace ownership check, cross-workspace read/update/delete IDOR
HIGH (8.1)
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an Insecure Direct Object Reference. The project CRUD endpoints (`GET / PATCH / DELETE /workspaces/{workspace_id}/projects/{project_id}` and `GET .../{project_id}/stats`) gate access on `require_workspace_member(workspace_id)` only, then resolve `project_id` through `ProjectService.get(project_id)` / `update(project_id, ...)` / `delete(project_id)` / `get_stats(project_id)`. None of these calls thread `workspace_id` through to constrain the lookup. A user who is a member of any workspace `W1` can read, modify, delete, or read stats for projects that belong to a different workspace `W2`. PraisonAI Platform version 0.1.4 patches the issue.
Published: 2026-07-21T17:26:45.841Z
Updated: 2026-07-22T18:27:07.254Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47417 vulnerable 2026-07-29 00:55:00.231642 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47416 vulnerable 2026-07-29 00:55:00.231532 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47415 vulnerable 2026-07-29 00:55:00.231415 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47414 vulnerable 2026-07-29 00:55:00.231295 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47413 vulnerable 2026-07-29 00:55:00.231065 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47412 vulnerable 2026-07-29 00:55:00.230822 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47411 vulnerable 2026-07-29 00:55:00.230572 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47410 vulnerable 2026-07-29 00:55:00.230433 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47409 vulnerable 2026-07-29 00:55:00.230257 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47408 vulnerable 2026-07-29 00:55:00.230057 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47407 vulnerable 2026-07-29 00:55:00.229868 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-47406 vulnerable 2026-07-29 00:55:00.229589 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.