MervinPraison PraisonAI up to 4.6.58 Streaming Execution TEMPLATE.yaml recipe.run_stream allow_dangerous_tools authorization

Summaryinfo

A vulnerability identified as problematic has been detected in MervinPraison PraisonAI up to 4.6.58. Affected by this issue is the function recipe.run_stream of the file TEMPLATE.yaml of the component Streaming Execution. Performing a manipulation of the argument allow_dangerous_tools results in authorization. This vulnerability is cataloged as CVE-2026-56838. The attack must be initiated from a local position. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in MervinPraison PraisonAI up to 4.6.58. It has been classified as problematic. This affects the function recipe.run_stream of the file TEMPLATE.yaml of the component Streaming Execution. The manipulation of the argument allow_dangerous_tools with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

PraisonAI is a multi-agent teams system. From version 4.5.87 to before version 4.6.59, PraisonAI recipe execution blocks default-denied dangerous tools unless the caller explicitly passes allow_dangerous_tools=True. The normal recipe.run() path enforces this with _check_tool_policy(). The streaming path, recipe.run_stream(), loads the same recipe, checks dependencies, and then calls _execute_recipe() without running the dangerous-tool policy check. As a result, a recipe that honestly declares execute_command in TEMPLATE.yaml requires.tools is denied by recipe.run(), but reaches the execution engine through recipe.run_stream() with allow_dangerous_tools=False. This issue has been patched in version 4.6.59.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-56838 since 06/23/2026. The exploitability is told to be easy. Attacking locally is a requirement. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 4.6.59 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• MervinPraison

Name

• PraisonAI

Version

• 4.6.0
• 4.6.1
• 4.6.2
• 4.6.3
• 4.6.4
• 4.6.5
• 4.6.6
• 4.6.7
• 4.6.8
• 4.6.9
• 4.6.10
• 4.6.11
• 4.6.12
• 4.6.13
• 4.6.14
• 4.6.15
• 4.6.16
• 4.6.17
• 4.6.18
• 4.6.19
• 4.6.20
• 4.6.21
• 4.6.22
• 4.6.23
• 4.6.24
• 4.6.25
• 4.6.26
• 4.6.27
• 4.6.28
• 4.6.29
• 4.6.30
• 4.6.31
• 4.6.32
• 4.6.33
• 4.6.34
• 4.6.35
• 4.6.36
• 4.6.37
• 4.6.38
• 4.6.39
• 4.6.40
• 4.6.41
• 4.6.42
• 4.6.43
• 4.6.44
• 4.6.45
• 4.6.46
• 4.6.47
• 4.6.48
• 4.6.49
• 4.6.50
• 4.6.51
• 4.6.52
• 4.6.53
• 4.6.54
• 4.6.55
• 4.6.56
• 4.6.57
• 4.6.58

Website

• Product: https://github.com/MervinPraison/PraisonAI/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion