{"answers":{"affected":"3 open source packages ship an affected version, including praisonai and PraisonAI. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39306 exists.","fix":"Upgrade praisonai to 4.5.113 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-39306 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39306 exists.\n\nAffected packages and fixed versions:\n- praisonai (PyPI): affected all versions; fixed in 4.5.113\n- praisonai (PyPI): affected all versions; fixed in 4.5.113\n- PraisonAI (PyPI): affected all versions; fixed in 4.5.113\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-39306/ (Markdown: https://insights.sbomify.com/CVE-2026-39306/index.md)","id":"CVE-2026-39306","markdown":"https://insights.sbomify.com/CVE-2026-39306/index.md","name":"CVE-2026-39306","record":{"aliases":["GHSA-4rx4-4r3x-6534","PYSEC-2026-2900"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PraisonAI Python library","requires_auth":"low_privilege","summary":"Attackers can write arbitrary files outside the target directory by crafting malicious recipe archives, affecting users pulling recipes from the registry.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"praisonai","vendor":"praison"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"PraisonAI recipe registry pull path traversal writes files outside the chosen output directory","id":"CVE-2026-39306","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"PraisonAI has an Arbitrary File Write (Zip Slip) in Templates Extraction","id":"CVE-2026-39307"},"packages":[{"ecosystem":"PyPI","fixed":["4.5.113"],"introduced":["0"],"last_affected":[],"package":"PraisonAI","purl":null,"source":"GHSA-4rx4-4r3x-6534"},{"ecosystem":"PyPI","fixed":["4.5.113"],"introduced":["0"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"GHSA-4rx4-4r3x-6534"},{"ecosystem":"PyPI","fixed":["4.5.113"],"introduced":["0"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"PYSEC-2026-2900"}],"prev":{"headline":"Arbitrary File Write / Path Traversal in Action Orchestrator","id":"CVE-2026-39305"},"products":["PraisonAI"],"published":"2026-04-07","related":[{"cvss_score":10,"headline":"PraisonAIAgents has a sandbox escape via exception frame traversal in `execute_code` (subprocess mode)","id":"CVE-2026-39888","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":9.8,"headline":"Incomplete fix for CVE-2026-34935: Command Injection in MervinPraison/PraisonAI","id":"CVE-2026-41497","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":9.8,"headline":"PraisonAI: Critical RCE via `type: job` workflow YAML","id":"CVE-2026-40288","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":9.8,"headline":"PraisonAI Affected by Remote Code Execution via YAML Deserialization in Agent Definition Loading","id":"CVE-2026-39890","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":9.8,"headline":"PraisonAI: Second-Order SQL Injection in `get_all_user_threads`","id":"CVE-2026-34934","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":9.8,"headline":"PraisonAI: OS Command Injection in MCPHandler.parse_mcp_command()","id":"CVE-2026-34935","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":9.7,"headline":"Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in praisonai","id":"CVE-2026-40088","kev_date_added":null,"published":"2026-04-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["MervinPraison"]},"summary":"Attackers can write arbitrary files outside the target directory by crafting malicious recipe archives, affecting users pulling recipes from the registry.","url":"https://insights.sbomify.com/CVE-2026-39306/"}