{"answers":{"affected":"3 open source packages ship an affected version, including praisonai and PraisonAI.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55540 exists.","fix":"Upgrade praisonai to 4.6.58 or later.","what":"CVE-2026-55540 is a high-severity path traversal vulnerability in MervinPraison PraisonAI, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-55540 and fix it if it is affected.\n\nWhat it is: CVE-2026-55540 is a high-severity path traversal vulnerability in MervinPraison PraisonAI, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, 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-55540 exists.\n\nAffected packages and fixed versions:\n- praisonai (PyPI): affected all versions; fixed in 4.6.58\n- praisonai (PyPI): affected all versions; fixed in 4.6.58\n- PraisonAI (PyPI): affected all versions; fixed in 4.6.58\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-55540/ (Markdown: https://insights.sbomify.com/CVE-2026-55540/index.md)","id":"CVE-2026-55540","markdown":"https://insights.sbomify.com/CVE-2026-55540/index.md","name":"CVE-2026-55540","record":{"aliases":["GHSA-ch89-h4r2-c8f8","PYSEC-2026-3888"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python AI agent library","requires_auth":"none","summary":"Attackers can read files outside the configured workspace by exploiting symlink handling in PraisonAI's path validation logic.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L","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 praisonai 4.6.51, is_path_within_directory() uses os.path.abspath() rather than os.path.realpath() for the workspace boundary. A symlink inside workspace can point outside and still pass the check, allowing read_file and other code tools to access files outside the configured workspace. This issue is fixed in version 4.6.58.","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: [Path Traversal] agent tools escape the configured workspace via symlinks","id":"CVE-2026-55540","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"PraisonAI: `--api-key` flag on `praisonai serve` is not properly enforced","id":"CVE-2026-55541"},"packages":[{"ecosystem":"PyPI","fixed":["4.6.58"],"introduced":["0"],"last_affected":[],"package":"PraisonAI","purl":null,"source":"GHSA-ch89-h4r2-c8f8"},{"ecosystem":"PyPI","fixed":["4.6.58"],"introduced":["0"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"GHSA-ch89-h4r2-c8f8"},{"ecosystem":"PyPI","fixed":["4.6.58"],"introduced":["0"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"PYSEC-2026-3888"}],"prev":{"headline":"PraisonAI: [Auth Bypass] PraisonAI async Jobs API (`/api/v1/runs`) has no authentication — unauthenticated job execution, result theft, cancel and delete","id":"CVE-2026-55539"},"products":["PraisonAI"],"published":"2026-08-25","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-08-27","vendors":["MervinPraison"]},"summary":"Attackers can read files outside the configured workspace by exploiting symlink handling in PraisonAI's path validation logic.","url":"https://insights.sbomify.com/CVE-2026-55540/"}