UTC
Critical

PraisonAI: Arbitrary File Read/Write via `multiedit` Tool Without Path Validation

CVE-2026-57145 · GHSA-29w3-p9w9-wc47 · published 2026-06-18 · updated 2026-07-20

Severity
Critical
CVSS score
9.1
Chance of exploitation (EPSS)
0.54%
Fixed in
4.6.61
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Total
  • CISA SSVC
What it is

An attacker who can influence the filepath parameter of the multiedit tool (via crafted prompts to an AI agent, user messages in Telegram/Discord/Slack bots using auto_approve_tools=True, or YAML workflow configurations) can: Read arbitrary files — any file readable by the process user, including secrets, SSH keys, cloud credentials, environment files (.env), and configuration files. Write/overwrite arbitrary files — modify any file writable by the process user, enabling privilege escalation (e.g., writing to ~/.bashrc, ~/.ssh/authorized_keys, or overwriting application source code). …

What to do

Upgrade praisonai to 4.6.61 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.

Apply the same path validation pattern used by file_tools.py and the code tools in src/praisonai/praisonai/code/tools/: 1. Add a _validate_path function that: Rejects paths containing .. Resolves symlinks via os.path.realpath Validates the resolved path is within the workspace/CWD using os.path.commonpath 2. Add protected path guards (.env, .git, .ssh, keys, credentials) 3. Apply _validate_path to the filepath parameter before any open() call 4. Consider adding @require_approval(risk_level="high") to the multiedit function

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI< 4.6.614.6.61
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].