{"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-47406 exists.","fix":"Upgrade praisonai-platform to 0.1.4 or later.","what":"CVE-2026-47406 is a high-severity missing authorization 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-47406 and fix it if it is affected.\n\nWhat it is: CVE-2026-47406 is a high-severity missing authorization 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-47406 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-47406/ (Markdown: https://insights.sbomify.com/CVE-2026-47406/index.md)","id":"CVE-2026-47406","markdown":"https://insights.sbomify.com/CVE-2026-47406/index.md","name":"CVE-2026-47406","record":{"aliases":["GHSA-4x6r-9v57-3gqw","PYSEC-2026-2928"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PraisonAI Platform","requires_auth":"low_privilege","summary":"Attackers can read, modify, or delete issues across different workspaces by manipulating IDs in dependency endpoints without proper ownership checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an Insecure Direct Object Reference. The dependency endpoints (`POST/GET /workspaces/{workspace_id}/issues/{issue_id}/dependencies` and `DELETE .../dependencies/{dep_id}`) gate access on `require_workspace_member(workspace_id)` only, then dispatch to `DependencyService` calls that take URL/body-supplied issue and dependency IDs without verifying any of them belong to the membership-checked workspace. Most damaging: `create_dependency` accepts `body.depends_on_issue_id` from the request body — that ID is checked against nothing — letting an attacker create a \"blocks\" or \"related\" link between any two issues anywhere in the database. 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: IDOR in dependency endpoints allows cross-workspace issue linking, reading, and deletion due to missing ownership checks","id":"CVE-2026-47406","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"PraisonAI Platform has a cross-workspace IDOR + member-role privilege escalation","id":"CVE-2026-47407"},"packages":[{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":null,"source":"GHSA-4x6r-9v57-3gqw"},{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":"pkg:pypi/praisonai-platform","source":"GHSA-4x6r-9v57-3gqw"},{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":"pkg:pypi/praisonai-platform","source":"PYSEC-2026-2928"}],"prev":{"headline":"PraisonAI Platform missing role checks let any workspace member become owner and take over workspace membership","id":"CVE-2026-47405"},"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":"Attackers can read, modify, or delete issues across different workspaces by manipulating IDs in dependency endpoints without proper ownership checks.","url":"https://insights.sbomify.com/CVE-2026-47406/"}