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
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.
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | <= 4.5.112 | 4.5.113 |
1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.
- io.github.MervinPraison/praisonaipraisonai@2.3.42
- 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.