UTC
High

PraisonAI recipe registry publish path traversal allows out-of-root file write

CVE-2026-39308 · GHSA-r9x3-wx45-2v7f · published 2026-04-06 · updated 2026-04-07

Severity
High
CVSS score
7.1
Chance of exploitation (EPSS)
0.34%
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 registry publish flow. Impacted parties: Registry operators running the PraisonAI recipe registry service. Any deployment that allows remote recipe publication. Any environment where adjacent writable filesystem locations contain sensitive application data, service files, or staged content that could be overwritten or planted. Security impact: Integrity impact is high because an attacker can create or overwrite files outside the registry root. Availability impact is possible if the attacker targets adjacent runtime or application files.

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. Validate manifest.json name and version before any path join or filesystem write. Reject path separators, .., absolute paths, and any value that fails the existing validatename() / validateversion() checks. 2. Resolve the final destination path and enforce that it remains under the configured registry root before calling mkdir() or copy2(). For example, compare the resolved destination against self.recipes_path.resolve(). 3. Move the URL-to-manifest consistency check ahead of self.registry.publish(...), or refactor publish() so it receives already-validated route parameters instead of trusting attacker-controlled manifest values for storage paths.

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