UTC
Medium

PraisonAI: ContextGatherer include resolution permits absolute and traversal reads outside the workspace

CVE-2026-61431 · GHSA-q7m5-3jmv-vm48 · published 2026-10-08

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

If a user or service runs PraisonAI context gathering on an attacker-influenced workspace, the attacker can cause local files outside the project root to be included in the generated context. Practical impacts include disclosure of source files from adjacent projects, local configuration, prompt transcripts, logs, API keys, and other process-readable text files with extensions that ContextGatherer considers relevant. If the context bundle is sent to an external model or exposed to a lower-trust caller, the file contents leave the intended workspace boundary. This report claims confidentiality impact only. It does not claim arbitrary write, command execution, or availability impact.

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.

Make include-file path resolution fail closed around a single workspace-containment helper: 1. Resolve the configured workspace root once with Path(self.directory).resolve(). 2. For each include entry, reject absolute paths outside the workspace. 3. Join relative include entries to the workspace, resolve the result, and require resolved.relativeto(workspaceroot) to succeed before opening or walking anything. 4. Apply the helper to both .praisoncontext and .praisoninclude processing. 5. Reject escaped directories as well as escaped files; process_path() can recursively walk directories. 6. Avoid appending file content before display/bookkeeping operations that can fail. 7.

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].