PT-2026-61757 · Praisonai · Praisonai

CVE-2026-56832

·

Published

2026-06-18

·

Updated

2026-07-23

CVSS v3.1

8.8

High

VectorAV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Name of the Vulnerable Software and Affected Versions praisonai versions 4.5.2 through 4.6.58
Description The praisonai.bots.DiscordApproval component improperly handles approval requests for dangerous tool calls. It approves a pending request if any non-bot message containing approval text, such as yes, is posted in the configured Discord channel after the approval request, regardless of whether the message is a direct reply or tied to the specific request. This lack of request binding allows any user with write access to the channel to authorize high-risk operations. Additionally, the Slack and Telegram approval backends lack an explicit approver allowlist. An attacker can exploit this to trigger privileged operations, potentially leading to code execution, file modification, or unauthorized data access with the privileges of the PraisonAI process. The issue occurs in the poll for response() function, which polls the endpoint /channels/{channel id}/messages?after={message id}&limit=10 and approves the request based on the content of subsequent messages without verifying the sender's identity or the message's relationship to the request.
Recommendations For versions 4.5.2 through 4.6.58:
  • Tie Discord approvals to specific requests by using Discord interactions, buttons with server-side request IDs, or requiring a reply where the message reference.message id matches the approval message.
  • Implement an explicit approver identity configuration, such as approver user ids or allowed approvers, across all messaging approval backends.
  • Configure the system to reject approvals from users not included in the authorized approver set.
  • Use a per-request nonce or opaque approval ID in callbacks to verify the request server-side before granting approval.
  • As a temporary mitigation, restrict write access to the configured approval channels to only trusted administrators.

Fix

Incorrect Authorization

Insufficient Verification of Data Authenticity

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-56832
GHSA-8579-RGG5-PH2M
PYSEC-2026-3506

Affected Products

Praisonai