UTC
Medium

PraisonAI: Project custom command templates can read outside-workspace files into model prompts

CVE-2026-60088 · GHSA-xpx6-x8c2-mw5w · published 2026-10-08

Severity
Medium
CVSS score
5.5
Chance of exploitation (EPSS)
0.22%
Fixed in
4.6.78
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

If the operator runs that project command, PraisonAI expands the outside file into the prompt. In normal use that prompt may be sent to a hosted model provider, logged, or displayed to a lower-trust caller. This report claims confidentiality impact only. It does not claim code execution, arbitrary write, credential theft without user interaction, persistence, or network scanning. Suggested severity: Medium under the local untrusted-repository threat model because the operator must run a project-defined command. Suggested CVSS 3.1 vector: Relevant CWEs: CWE-22: Improper Limitation of a Pathname to a Restricted Directory CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

What to do

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

Resolve command @path references through a single containment helper before opening files: 1. Resolve the project root or intended command workspace once. 2. For relative references, join to that root and then call resolve(). 3. For absolute references, either reject them outright or require resolved.relativeto(root) to succeed. 4. Reject escaped files before any exists(), isfile(), or open() operation. 5. Apply the same boundary to project and user command templates. 6. Minimal shape:

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