{"answers":{"affected":"3 open source packages ship an affected version, including praisonai. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40156 exists.","fix":"Upgrade praisonai to 4.5.128 or later.","what":"CVE-2026-40156 is a high-severity code injection vulnerability in MervinPraison PraisonAI, published on 10 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-40156 and fix it if it is affected.\n\nWhat it is: CVE-2026-40156 is a high-severity code injection vulnerability in MervinPraison PraisonAI, published on 10 Apr 2026. It can only be exploited from the same machine or local 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-40156 exists.\n\nAffected packages and fixed versions:\n- praisonai (PyPI): affected all versions; fixed in 4.5.128\n- praisonai (PyPI): affected all versions; fixed in 4.5.128\n- praisonai (PyPI): affected all versions; fixed in 4.5.128\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-40156/ (Markdown: https://insights.sbomify.com/CVE-2026-40156/index.md)","id":"CVE-2026-40156","markdown":"https://insights.sbomify.com/CVE-2026-40156/index.md","name":"CVE-2026-40156","record":{"aliases":["GHSA-2g3w-cpc4-chr4","PYSEC-2026-2895"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python AI agent library","requires_auth":"none","summary":"Attackers can execute arbitrary code by placing a malicious tools.py file in the working directory, affecting users running PraisonAI.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"praisonai","vendor":"praison"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"},{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"PraisonAI is a multi-agent teams system. Prior to 4.5.128, PraisonAI automatically loads a file named tools.py from the current working directory to discover and register custom agent tools. This loading process uses importlib.util.spec_from_file_location and immediately executes module-level code via spec.loader.exec_module() without explicit user consent, validation, or sandboxing. The tools.py file is loaded implicitly, even when it is not referenced in configuration files or explicitly requested by the user. As a result, merely placing a file named tools.py in the working directory is sufficient to trigger code execution. This behavior violates the expected security boundary between user-controlled project files (e.g., YAML configurations) and executable code, as untrusted content in the working directory is treated as trusted and executed automatically. If an attacker can place a malicious tools.py file into a directory where a user or automated system (e.g., CI/CD pipeline) runs praisonai, arbitrary code execution occurs immediately upon startup, before any agent logic begins.  This vulnerability is fixed in 4.5.128.","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 Affected by Implicit Execution of Arbitrary Code via Automatic `tools.py` Loading","id":"CVE-2026-40156","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"PraisonAI affected by arbitrary file write via path traversal in `praisonai recipe unpack`","id":"CVE-2026-40157"},"packages":[{"ecosystem":"PyPI","fixed":["4.5.128"],"introduced":["0"],"last_affected":[],"package":"praisonai","purl":null,"source":"GHSA-2g3w-cpc4-chr4"},{"ecosystem":"PyPI","fixed":["4.5.128"],"introduced":["0"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"GHSA-2g3w-cpc4-chr4"},{"ecosystem":"PyPI","fixed":["4.5.128"],"introduced":["0"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"PYSEC-2026-2895"}],"prev":{"headline":"Auth0 Next.js SDK has Improper Proxy Cache Lookup","id":"CVE-2026-40155"},"products":["PraisonAI"],"published":"2026-04-10","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":"total"},"state":"PUBLISHED","updated":"2026-04-13","vendors":["MervinPraison"]},"summary":"Attackers can execute arbitrary code by placing a malicious tools.py file in the working directory, affecting users running PraisonAI.","url":"https://insights.sbomify.com/CVE-2026-40156/"}