UTC
High

PraisonAI Dynamic Context history and terminal tools read files outside configured storage via path traversal

CVE-2026-56833 · GHSA-22cj-m4wf-fv2c · published 2026-06-18 · updated 2026-07-20

Severity
High
CVSS score
7.5
Chance of exploitation (EPSS)
0.46%
Fixed in
4.6.59
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

If a PraisonAI application exposes these Dynamic Context tools to untrusted or lower-trust prompts, the lower-trust caller can read files outside the configured context storage when the target file can be reached with the tool-imposed suffix: history_* tools can disclose reachable .jsonl files; terminal_* tools can disclose reachable .log files; and cross-run or cross-agent context/history/logs can be disclosed if their path is known or guessable. This can expose conversation history, prompts, terminal output, command logs, tokens, API keys, cloud credentials, operational data, or other secrets stored in JSONL/log files readable by the PraisonAI process. …

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.

Treat run_id and agent_id as logical identifiers, not path components. Recommended fixes: 1. Reject absolute paths, path separators, and traversal components in run_id and agent_id. 2. Build candidate paths, call .resolve(), and reject any path that is not under self.base_dir.resolve(). 3. Apply the same containment helper to history append/read/search/clear/export and terminal log/read/search/clear/export paths. 4. Prefer opaque server-generated run and agent IDs in tool schemas. 5. Pair this with an identifier allowlist, because run_id and agent_id should not need filesystem syntax.

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