CVE-2026-39306

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

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.
• The issue crosses a real security boundary because the attacker only needs to publish a malicious recipe, while the victim triggers the write by pulling it.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-39306 has a CVSS score of 7.3 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.5.113); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-39306? CVE-2026-39306 is a high-severity path traversal vulnerability in PraisonAI (pip), affecting versions <= 4.5.112. It is fixed in 4.5.113. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-39306? CVE-2026-39306 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of PraisonAI are affected by CVE-2026-39306? PraisonAI (pip) versions <= 4.5.112 is affected.
4. Is there a fix for CVE-2026-39306? Yes. CVE-2026-39306 is fixed in 4.5.113. Upgrade to this version or later.
5. Is CVE-2026-39306 exploitable, and should I be worried? Whether CVE-2026-39306 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-39306 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-39306? Upgrade PraisonAI to 4.5.113 or later.