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
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.
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | <= 4.6.77 | 4.6.78 |
1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.
- io.github.MervinPraison/praisonaipraisonai@2.3.42
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
- 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.