https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:03:19 +0000 https://cve.radiocsirt.org/vuln/cve-2026-44336 <p><strong>Affected:</strong> MervinPraison PraisonAI</p> <p>PraisonAI is a multi-agent teams system. Prior to version 4.6.34, PraisonAI&#39;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[&#34;arguments&#34;] blind to each handler via **kwargs without validating against the advertised input schema. By setting rule_name=&#34;../../&lt;some-path&gt;&#34; 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&#39;s python REPL, or any background Python service. This issue has been patched in version 4.6.34.</p> <p><strong>Affected:</strong> MervinPraison PraisonAI</p> <p>PraisonAI is a multi-agent teams system. Prior to version 4.6.34, PraisonAI&#39;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[&#34;arguments&#34;] blind to each handler via **kwargs without validating against the advertised input schema. By setting rule_name=&#34;../../&lt;some-path&gt;&#34; 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&#39;s python REPL, or any background Python service. This issue has been patched in version 4.6.34.</p> https://cve.radiocsirt.org/vuln/cve-2026-44336 https://cve.radiocsirt.org/vuln/ghsa-9mqq-jqxf-grvw <p><strong>Affected:</strong> PyPI: PraisonAI</p> <p>## Summary</p> <p>PraisonAI&#39;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[&#34;arguments&#34;]` blind to each handler via `**kwargs` without validating against the advertised input schema.</p> <p>By setting `rule_name=&#34;../../&lt;some-path&gt;&#34;` 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&#39;s `python` REPL, or any background Python service. The same primitive is reachable from:</p> <p>- An MCP-connected LLM (Claude Desktop, Cursor, Continue.dev, Claude Code) whose context is poisoned by attacker-controlled web content / documents / emails — **no operator click required beyond ordinary &#34;ask the LLM to summarise this page&#34; usage**. - `praisonai mcp serve --transport http-stream` with no `--api-key` (default), reachable from any local process / DNS-rebound browser tab / container neighbour sharing loopback. - Stdio MCP from any promp…</p> <p><strong>Affected:</strong> PyPI: PraisonAI</p> <p>## Summary</p> <p>PraisonAI&#39;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[&#34;arguments&#34;]` blind to each handler via `**kwargs` without validating against the advertised input schema.</p> <p>By setting `rule_name=&#34;../../&lt;some-path&gt;&#34;` 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&#39;s `python` REPL, or any background Python service. The same primitive is reachable from:</p> <p>- An MCP-connected LLM (Claude Desktop, Cursor, Continue.dev, Claude Code) whose context is poisoned by attacker-controlled web content / documents / emails — **no operator click required beyond ordinary &#34;ask the LLM to summarise this page&#34; usage**. - `praisonai mcp serve --transport http-stream` with no `--api-key` (default), reachable from any local process / DNS-rebound browser tab / container neighbour sharing loopback. - Stdio MCP from any promp…</p> https://cve.radiocsirt.org/vuln/ghsa-9mqq-jqxf-grvw