MervinPraison PraisonAI up to 4.6.33 Model Context Protocol input validation

Summaryinfo

A vulnerability marked as critical has been reported in MervinPraison PraisonAI up to 4.6.33. This issue affects the function PraisonAI.rules.create/PraisonAI.rules.show/PraisonAI.rules.delete/PraisonAI.workflow.show of the component Model Context Protocol. The manipulation leads to input validation. This vulnerability is referenced as CVE-2026-44336. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in MervinPraison PraisonAI up to 4.6.33. This issue affects the function PraisonAI.rules.create/PraisonAI.rules.show/PraisonAI.rules.delete/PraisonAI.workflow.show of the component Model Context Protocol. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

PraisonAI is a multi-agent teams system. Prior to version 4.6.34, PraisonAI's MCP (Model Context Protocol) server (praisonai mcp serve) registers four file-handling tools by default — praisonai.rules.create, praisonai.rules.show, praisonai.rules.delete, and praisonai.workflow.show. Each accepts a path or filename string from MCP tools/call arguments and joins it onto ~/.praison/rules/ (or, for workflow.show, accepts an absolute path) with no containment check. The JSON-RPC dispatcher passes params["arguments"] blind to each handler via **kwargs without validating against the advertised input schema. By setting rule_name="../../" an attacker walks out of the rules directory and writes any file the running user can write. Dropping a Python .pth file into the user site-packages directory escalates this primitive to arbitrary code execution in any subsequent Python process the user spawns — the next praisonai CLI invocation, an IDE script run, the user's python REPL, or any background Python service. This issue has been patched in version 4.6.34.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-44336 since 05/05/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. 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.34 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

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