UTC
High

PraisonAI recipe registry pull path traversal writes files outside the chosen output directory

CVE-2026-39306 · GHSA-4rx4-4r3x-6534 · published 2026-04-06 · updated 2026-04-07

Severity
High
CVSS score
7.3
Chance of exploitation (EPSS)
0.30%
Fixed in
4.5.113
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

This is a path traversal / arbitrary file write vulnerability in the recipe pull workflow. Impacted parties: Users who pull recipes from an untrusted or shared PraisonAI registry. Teams running internal registries where one publisher can influence what other users pull. Automated systems or CI jobs that fetch recipes into working directories near sensitive project files. Security impact: Integrity impact is high because an attacker can create or overwrite files outside the expected extraction directory. Availability impact is significant if the overwritten target is a config file, project file, startup script, or another operational artifact.

What to do

Upgrade praisonai to 4.5.113 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.

1. Replace raw tar.extractall() with a safe extraction routine that validates every TarInfo member before extraction. Reject absolute paths, .. segments, and any resolved path that escapes the intended extraction directory. 2. Apply the same archive member validation in both LocalRegistry.pull() and HttpRegistry.pull() so that local and remote registry clients share the same safety guarantees. 3. Consider validating tar contents during publish as well, so malicious bundles are rejected before they ever enter the registry and cannot be served to downstream users.

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI<= 4.5.1124.5.113
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].