CVE-2026-47417
Deferred Deferred - Pending Action

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 comment endpoints (`POST /workspaces/{workspace_id}/issues/{issue_id}/comments` and `GET .../comments`) gate access on `require_workspace_member(workspace_id)` only, then call `CommentService.create(issue_id=issue_id, ...)` and `CommentService.list_for_issue(issue_id)` without verifying that `issue_id` belongs to `workspace_id`. A user who is a member of any workspace `W1` can read every comment on, and post new comments to, any issue in any other workspace `W2`. 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-47417
EUVD
EUVD-2026-46335

Affected Vendors & Products

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

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in the PraisonAI Platform. It allows a user who is a member of any workspace to read comments from and post comments to issues in any other workspace without proper ownership verification. The issue exists because the comment endpoints only check workspace membership but do not validate that the issue belongs to the specified workspace.

Detection Guidance

To detect this vulnerability, check if your PraisonAI Platform version is below 0.1.4. Review API logs for unauthorized access attempts to comment endpoints across different workspaces. Look for requests to POST /workspaces/{workspace_id}/issues/{issue_id}/comments or GET .../comments where the issue_id does not belong to the workspace_id.

Impact Analysis

An attacker who is a member of any workspace can exploit this flaw to read sensitive comments on issues in other workspaces, including bug reports with secrets or customer personal information. They can also inject malicious comments under their identity into foreign issues, potentially leading to data breaches or misinformation.

Compliance Impact

This vulnerability could lead to unauthorized access to personal or sensitive data, violating GDPR's data protection principles and HIPAA's requirements for safeguarding protected health information. Organizations using affected versions may face compliance violations, legal penalties, and reputational damage.

Mitigation Strategies

Immediately upgrade PraisonAI Platform to version 0.1.4 or later. Ensure all API endpoints enforce workspace-scoped issue validation before allowing comment operations. Review and restrict workspace memberships to minimize potential attack surfaces.

Chat Assistant

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

EPSS Chart