MervinPraison PraisonAI up to 4.6.60 YAMLWorkflowParser workflow.yaml Workflow.start access control

Summaryinfo

A vulnerability was found in MervinPraison PraisonAI up to 4.6.60. It has been classified as critical. This vulnerability affects the function Workflow.start of the file workflow.yaml of the component YAMLWorkflowParser. Performing a manipulation results in access control. This vulnerability was named CVE-2026-57142. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as critical, was found in MervinPraison PraisonAI up to 4.6.60. This affects the function Workflow.start of the file workflow.yaml of the component YAMLWorkflowParser. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. 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.61, PraisonAI recipe execution has a dangerous-tool policy that is supposed to block default-denied tools unless the caller explicitly passes allow_dangerous_tools=True. That policy only checks tools declared in TEMPLATE.yaml requires.tools. For steps-based recipes, the actual execution path loads workflow.yaml with YAMLWorkflowParser. That parser resolves agent-level tools: declarations and preserves top-level approve:. Workflow.start() then installs those YAML-approved tools into the approval context. As a result, an untrusted recipe can omit execute_command from TEMPLATE.yaml requires.tools, declare it in workflow.yaml agents.*.tools, and add top-level approve: [execute_command]. The caller did not set allow_dangerous_tools=True, but the recipe policy allows the recipe and the workflow approval path self-approves the critical shell tool. This issue has been patched in version 4.6.61.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-57142 since 06/24/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

Upgrading to version 4.6.61 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
• 4.6.59
• 4.6.60

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