UTC
High

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
What it is

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.

What to do

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().

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI>= 3.8.1, <= 4.6.584.6.59

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