{"answers":{"affected":"3 open source packages ship an affected version, including praisonai-platform.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47405 exists.","fix":"Upgrade praisonai-platform to 0.1.4 or later.","what":"CVE-2026-47405 is a high-severity vulnerability in MervinPraison praisonai-platform, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47405 and fix it if it is affected.\n\nWhat it is: CVE-2026-47405 is a high-severity vulnerability in MervinPraison praisonai-platform, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47405 exists.\n\nAffected packages and fixed versions:\n- praisonai-platform (PyPI): affected all versions; fixed in 0.1.4\n- praisonai-platform (PyPI): affected all versions; fixed in 0.1.4\n- praisonai-platform (PyPI): affected all versions; fixed in 0.1.4\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-47405/ (Markdown: https://insights.sbomify.com/CVE-2026-47405/index.md)","id":"CVE-2026-47405","markdown":"https://insights.sbomify.com/CVE-2026-47405/index.md","name":"CVE-2026-47405","record":{"aliases":["GHSA-h37g-4h4p-9x97","PYSEC-2026-2936"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"PraisonAI Platform","requires_auth":"low_privilege","summary":"Authenticated workspace members can escalate privileges to owner and take over workspace membership due to missing role checks in administrative routes.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have a broken workspace authorization check that allows any authenticated low-privilege workspace member to escalate their own role to `owner`. The issue is caused by privileged workspace-management routes using the shared dependency `require_workspace_member(...)` without requiring `admin` or `owner`. The dependency defaults to `min_role=\"member\"`, so routes that should be administrative are accessible to ordinary workspace members. As a result, a normal workspace member can promote their own account from `member` to `owner`; add arbitrary users as `owner` or `admin`; change other members' roles; remove legitimate owners or members; take over workspace membership completely; and/or perform destructive workspace operations after escalation. This is a broken access control / vertical privilege escalation vulnerability. PraisonAI Platform version 0.1.4 patches 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 Platform missing role checks let any workspace member become owner and take over workspace membership","id":"CVE-2026-47405","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"praisonai-platform: IDOR in dependency endpoints allows cross-workspace issue linking, reading, and deletion due to missing ownership checks","id":"CVE-2026-47406"},"packages":[{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":null,"source":"GHSA-h37g-4h4p-9x97"},{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":"pkg:pypi/praisonai-platform","source":"GHSA-h37g-4h4p-9x97"},{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":"pkg:pypi/praisonai-platform","source":"PYSEC-2026-2936"}],"prev":{"headline":"PraisonAI Platform workspace-scoped routes allow cross-workspace object access by global object ID","id":"CVE-2026-47399"},"products":["praisonai-platform"],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-21","vendors":["MervinPraison"]},"summary":"Authenticated workspace members can escalate privileges to owner and take over workspace membership due to missing role checks in administrative routes.","url":"https://insights.sbomify.com/CVE-2026-47405/"}