{"answers":{"affected":"3 open source packages ship an affected version, including praisonai.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57144 exists.","fix":"Upgrade praisonai to 4.6.61 or later.","what":"CVE-2026-57144 is a high-severity vulnerability in MervinPraison PraisonAI, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-57144 and fix it if it is affected.\n\nWhat it is: CVE-2026-57144 is a high-severity vulnerability in MervinPraison PraisonAI, published on 23 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57144 exists.\n\nAffected packages and fixed versions:\n- praisonai (PyPI): affected from 4.5.110; fixed in 4.6.61\n- praisonai (PyPI): affected from 4.5.110; fixed in 4.6.61\n- praisonai (PyPI): affected from 4.5.110; fixed in 4.6.61\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-57144/ (Markdown: https://insights.sbomify.com/CVE-2026-57144/index.md)","id":"CVE-2026-57144","markdown":"https://insights.sbomify.com/CVE-2026-57144/index.md","name":"CVE-2026-57144","record":{"aliases":["GHSA-6jcq-6546-qrrw","PYSEC-2026-3504"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"},{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"},{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"PraisonAI is a multi-agent teams system. From version 4.5.110 to before version 4.6.61, praisonai.sandbox.SandlockSandbox is documented and implemented as the kernel-enforced sandbox backend for untrusted code. Its SandboxConfig.native() path lets callers configure allowed filesystem paths and network=False. On systems where the optional sandlock module imports but reports that Landlock is unavailable, SandlockSandbox.execute() and run_command() do not fail closed. They silently fall back to SubprocessSandbox(self.config). That fallback keeps the same high-level native policy object but does not enforce the native filesystem or network boundary during code execution. A sandboxed payload can read files outside the configured allowed path and open network connections despite network=False. This issue has been patched in version 4.6.61.","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 SandlockSandbox falls back to unrestricted subprocess execution when Landlock is unavailable","id":"CVE-2026-57144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"PraisonAI: Arbitrary File Read/Write via `multiedit` Tool Without Path Validation","id":"CVE-2026-57145"},"packages":[{"ecosystem":"PyPI","fixed":["4.6.61"],"introduced":["4.5.110"],"last_affected":[],"package":"praisonai","purl":null,"source":"GHSA-6jcq-6546-qrrw"},{"ecosystem":"PyPI","fixed":["4.6.61"],"introduced":["4.5.110"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"GHSA-6jcq-6546-qrrw"},{"ecosystem":"PyPI","fixed":["4.6.61"],"introduced":["4.5.110"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"PYSEC-2026-3504"}],"prev":{"headline":"PraisonAI: Server-Side Request Forgery (SSRF) in SearxNG / search_web tools via attacker-controlled searxng_url parameter","id":"CVE-2026-57143"},"products":["PraisonAI"],"published":"2026-10-23","related":[],"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":"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-10-29","vendors":["MervinPraison"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-57144/"}