PraisonAI dynamic-context artifact tools read arbitrary host files outside artifact storage
CVE-2026-56834 · GHSA-j7qx-p75m-wp7g · published 2026-06-18 · updated 2026-07-20
- Severity
- High
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- 0.37%
- Fixed in
- 4.6.59
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
If a PraisonAI application exposes an agent with ctx.get_tools() to untrusted or lower-trust prompts, the lower-trust caller can request artifact tools against arbitrary local paths. This can disclose sensitive host files readable by the PraisonAI process, including: project .env files; cloud or service credentials; SSH keys; local application configuration; source files and private data; and terminal/history artifacts from other runs if the path is known or guessed. The impact is confidentiality-only in the tested surface. Integrity and availability are not claimed for this report.
Upgrade praisonai to 4.6.59 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.
Do not let artifact tools open arbitrary paths. Prefer stable artifact IDs over raw filesystem paths in tool arguments. Recommended fixes: 1. Change tool schemas to accept artifactid plus optional runid and agentid, then resolve those through the artifact store's metadata/index. 2. If path arguments must remain for compatibility, resolve the path with Path(path).resolve() and reject it unless it is under artifactstore.base_dir.resolve(). 3. Require a valid artifact metadata sidecar for read helpers. Files not created by FileSystemArtifactStore.store() should not be readable through artifact tools. 4. Apply the same containment check to load(), head(), tail(), grep(), chunk(), and delete().
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | >= 3.8.1, <= 4.6.58 | 4.6.59 |
- 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.