CVE-2026-47406
Received Received - Intake

Insecure Direct Object Reference in PraisonAI Platform

Publication date: 2026-07-21

Last updated on: 2026-07-21

Assigner: GitHub, Inc.

Description
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 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. PraisonAI Platform version 0.1.4 patches the issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-21
Last Modified
2026-07-21
Generated
2026-07-21
AI Q&A
2026-07-21
EPSS Evaluated
N/A
NVD
CVE-2026-47406
EUVD
EUVD-2026-46315

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
praisonai praisonai_platform to 0.1.4 (exc)
mervinpraison praisonai_platform to 0.1.4 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-47406 is an Insecure Direct Object Reference (IDOR) vulnerability in the PraisonAI Platform. It affects dependency endpoints that manage issue relationships within workspaces. The flaw allows attackers to manipulate issue dependencies across different workspaces without proper ownership verification. Specifically, endpoints for creating, listing, and deleting dependencies do not validate if issue IDs belong to the authenticated user's workspace, enabling unauthorized cross-workspace dependency changes.

Detection Guidance

To detect this IDOR vulnerability in PraisonAI Platform, inspect API logs for unauthorized dependency manipulations between workspaces. Check for requests to endpoints like POST/GET /workspaces/{workspace_id}/issues/{issue_id}/dependencies or DELETE /dependencies/{dep_id} where issue IDs do not belong to the authenticated user's workspace. Look for anomalies such as cross-workspace issue linking or deletions without proper ownership validation.

Impact Analysis

An attacker with membership in any workspace can exploit this to link unrelated issues between different workspaces, disrupting workflows or deleting legitimate dependencies. This could lead to data integrity issues, unauthorized access to sensitive information, or workflow disruptions. The attack requires low privileges and network access but no user interaction.

Compliance Impact

This vulnerability could lead to unauthorized access or manipulation of sensitive data, potentially violating GDPR's data integrity and confidentiality requirements or HIPAA's access controls. Organizations using PraisonAI Platform may face compliance risks due to potential data breaches or unauthorized modifications.

Mitigation Strategies

Upgrade PraisonAI Platform to version 0.1.4 or later to patch the insecure direct object reference vulnerability in dependency endpoints.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-47406. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart