PraisonAI MCP `tools/call` path-traversal => RCE via Python `.pth` injection
CVE-2026-44336 · GHSA-9mqq-jqxf-grvw · published 2026-05-11 · updated 2026-11-16
- Severity
- Critical
- CVSS score
- 9.6
- Chance of exploitation (EPSS)
- 0.62%
- Fixed in
- 4.6.34
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
Arbitrary code execution on the user's machine, with the user's privileges, on any subsequent Python process they start. The .pth payload mechanism makes execution reliable and decoupled in time from the write — the user is not necessarily running praisonai when the payload fires; the next python invocation suffices. Arbitrary file read of any file the user can read — including ~/.ssh/, ~/.aws/credentials, ~/.config/praisonai/.yaml, environment files, credential stores, source code, browser profiles, IDE workspace state.
Upgrade praisonai to 4.6.34 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
1. Containment in every clitools handler. Replace bare os.path.join / f-string interpolation with explicit prefix validation: Apply identically to praisonai.rules.create, rules.show, rules.delete, workflow.validate. For workflow.show, restrict filepath to a designated workflow directory and reject absolute paths or any value containing ... 2. Schema enforcement in the dispatcher. Validate params["arguments"] against tool.inputschema (a JSON-Schema validator such as jsonschema) before tool.handler(arguments). Reject unknown properties, type mismatches, missing required fields. Return JSON-RPC -32602 Invalid params. 3. Reduce the default tool surface. Move rules.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | <= 4.6.33 | 4.6.34 |
1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.
- io.github.MervinPraison/praisonaipraisonai@2.3.42
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- CriticalPraisonAI: AICoder Arbitrary File Write and Command Execution via LLM Tool Callspraisonai
- CriticalPraisonAI: Code Injection via f-string Interpolation in Deploy API Server Generationpraisonai
- CriticalPraisonAI has a Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92praisonai
- CriticalPraisonAI: Arbitrary File Read/Write via `multiedit` Tool Without Path Validationpraisonai
- CriticalPraisonAI: Unauthenticated RCE via Jobs API + Approval Bypasspraisonaiagents, praisonai
- CriticalPraisonAI: AgentOS remains unauthenticated after incomplete fix version and allows remote agent invocationpraisonai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.