{"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-47393 exists.","fix":"Upgrade praisonai to 4.6.40 or later.","what":"CVE-2026-47393 is a critical missing authorization vulnerability in MervinPraison PraisonAI, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47393 and fix it if it is affected.\n\nWhat it is: CVE-2026-47393 is a critical missing authorization vulnerability in MervinPraison PraisonAI, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47393 exists.\n\nAffected packages and fixed versions:\n- praisonai (PyPI): affected all versions; fixed in 4.6.40\n- praisonai (PyPI): affected all versions; fixed in 4.6.40\n- PraisonAI (PyPI): affected all versions; fixed in 4.6.40\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-47393/ (Markdown: https://insights.sbomify.com/CVE-2026-47393/index.md)","id":"CVE-2026-47393","markdown":"https://insights.sbomify.com/CVE-2026-47393/index.md","name":"CVE-2026-47393","record":{"aliases":["GHSA-8444-4fhq-fxpq","PYSEC-2026-465"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python AI agent library","requires_auth":"none","summary":"PraisonAI's default API server configuration lacks authentication, allowing unauthenticated attackers to access endpoints and potentially execute code via LLM orchestration.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"},{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"PraisonAI is a multi-agent teams system. CVE-2026-44338 (GHSA-6rmh-7xcm-cpxj) documents that PraisonAI ships a code-generator (`praisonai.deploy.api.generate_api_server_code`) that emits a Flask API server with authentication disabled by default. Users who follow the documented quickstart (`praisonai deploy --type api`) get a server that binds to `0.0.0.0` per the recommended sample YAML, exposes `/chat` and `/agents` endpoints, runs `praisonai.run()` on user-supplied JSON input — LLM orchestration with the API key materials present in the process environment, and does not require any authentication. Versions prior to 4.6.40 still ship the generator with `auth_enabled` defaulting to `False`. The fix shape is opt-in via `APIConfig(auth_enabled=True, auth_token=...)`. Version 4.6.40 fixes the issue.","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 `deploy --type api` emits a Flask server with authentication disabled by default","id":"CVE-2026-47393","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"PraisonAI vulnerable to unauthenticated arbitrary file read via MCP workflow.show, workflow.validate, deploy.validate","id":"CVE-2026-47394"},"packages":[{"ecosystem":"PyPI","fixed":["4.6.40"],"introduced":["0"],"last_affected":[],"package":"PraisonAI","purl":null,"source":"GHSA-8444-4fhq-fxpq"},{"ecosystem":"PyPI","fixed":["4.6.40"],"introduced":["0"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"GHSA-8444-4fhq-fxpq"},{"ecosystem":"PyPI","fixed":["4.6.40"],"introduced":["0"],"last_affected":[],"package":"praisonai","purl":"pkg:pypi/praisonai","source":"PYSEC-2026-465"}],"prev":{"headline":"PraisonAI vulnerable to sandbox escape via `print.__self__` builtins module leak in `execute_code` (subprocess mode)","id":"CVE-2026-47392"},"products":["PraisonAI"],"published":"2026-07-21","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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["MervinPraison"]},"summary":"PraisonAI's default API server configuration lacks authentication, allowing unauthenticated attackers to access endpoints and potentially execute code via LLM orchestration.","url":"https://insights.sbomify.com/CVE-2026-47393/"}