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

High 7.3 Published Updated

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

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

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

Which versions are affected by CVE-2026-39306?

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

PackageAffectedFixed in
praisonai PyPIAll versions4.5.113
praisonai PyPIAll versions4.5.113
PraisonAI PyPIAll versions4.5.113

Products include Praison Praisonai.

How do I fix CVE-2026-39306?

Upgrade praisonai to 4.5.113 or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-39306 being exploited?

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

Sources

Also known as GHSA-4rx4-4r3x-6534, PYSEC-2026-2900.

Is CVE-2026-39306 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free