# CVE-2026-39306: PraisonAI recipe registry pull path traversal writes files outside the chosen output directory

> Attackers can write arbitrary files outside the target directory by crafting malicious recipe archives, affecting users pulling recipes from the registry.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-4rx4-4r3x-6534, PYSEC-2026-2900

## What is CVE-2026-39306?

CVE-2026-39306 is a high-severity path traversal vulnerability in MervinPraison PraisonAI, published on 7 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

PraisonAI is a multi-agent teams system. Prior to 1.5.113, PraisonAI's recipe registry pull flow extracts attacker-controlled .praison tar archives with tar.extractall() and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains ../ traversal entries and any user who later pulls that recipe will write files outside the output directory they selected. This is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself. This vulnerability is fixed in 1.5.113.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-39306?

3 open source packages ship an affected version, including praisonai and PraisonAI. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonai` | PyPI | All versions | 4.5.113 |
| `praisonai` | PyPI | All versions | 4.5.113 |
| `PraisonAI` | PyPI | All versions | 4.5.113 |

Products: Praison Praisonai.

## How do I fix CVE-2026-39306?

Upgrade praisonai to 4.5.113 or later.

## Is CVE-2026-39306 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39306 exists.

## Other vulnerabilities in MervinPraison PraisonAI

- [CVE-2026-39888](https://insights.sbomify.com/CVE-2026-39888/): PraisonAIAgents has a sandbox escape via exception frame traversal in `execute_code` (subprocess mode) (critical 10.0)
- [CVE-2026-41497](https://insights.sbomify.com/CVE-2026-41497/): Incomplete fix for CVE-2026-34935: Command Injection in MervinPraison/PraisonAI (critical 9.8)
- [CVE-2026-40288](https://insights.sbomify.com/CVE-2026-40288/): PraisonAI: Critical RCE via `type: job` workflow YAML (critical 9.8)
- [CVE-2026-39890](https://insights.sbomify.com/CVE-2026-39890/): PraisonAI Affected by Remote Code Execution via YAML Deserialization in Agent Definition Loading (critical 9.8)
- [CVE-2026-34934](https://insights.sbomify.com/CVE-2026-34934/): PraisonAI: Second-Order SQL Injection in `get_all_user_threads` (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39306 and fix it if it is affected.

What it is: CVE-2026-39306 is a high-severity path traversal vulnerability in MervinPraison PraisonAI, published on 7 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39306 exists.

Affected packages and fixed versions:
- praisonai (PyPI): affected all versions; fixed in 4.5.113
- praisonai (PyPI): affected all versions; fixed in 4.5.113
- PraisonAI (PyPI): affected all versions; fixed in 4.5.113

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-39306/ (Markdown: https://insights.sbomify.com/CVE-2026-39306/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-39306
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-39306
- OSV: https://osv.dev/vulnerability/CVE-2026-39306

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-39306/
Summaries are generated and may contain mistakes; the official description above is the record.