UTC
Critical

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
What it is

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.

What to do

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.

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI<= 4.6.334.6.34
Downstream in the Official MCP Registry

1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.

  • io.github.MervinPraison/praisonaipraisonai@2.3.42
See the trace →

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].