{"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-47417 exists.","fix":"Upgrade praisonai-platform to 0.1.4 or later.","what":"CVE-2026-47417 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-47417 and fix it if it is affected.\n\nWhat it is: CVE-2026-47417 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-47417 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-47417/ (Markdown: https://insights.sbomify.com/CVE-2026-47417/index.md)","id":"CVE-2026-47417","markdown":"https://insights.sbomify.com/CVE-2026-47417/index.md","name":"CVE-2026-47417","record":{"aliases":["GHSA-cp4f-5m9r-5jc2","PYSEC-2026-2933"],"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 and post comments on issues in other workspaces due to missing ownership checks, affecting PraisonAI Platform users.","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 comment endpoints (`POST /workspaces/{workspace_id}/issues/{issue_id}/comments` and `GET .../comments`) gate access on `require_workspace_member(workspace_id)` only, then call `CommentService.create(issue_id=issue_id, ...)` and `CommentService.list_for_issue(issue_id)` without verifying that `issue_id` belongs to `workspace_id`. A user who is a member of any workspace `W1` can read every comment on, and post new comments to, any issue in any other workspace `W2`. 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: Comment endpoints accept any issue_id without workspace ownership check, cross-workspace comment read and post IDOR","id":"CVE-2026-47417","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"praisonai-platform: Project endpoints accept any project_id without workspace ownership check, cross-workspace read/update/delete IDOR","id":"CVE-2026-47418"},"packages":[{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":null,"source":"GHSA-cp4f-5m9r-5jc2"},{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":"pkg:pypi/praisonai-platform","source":"GHSA-cp4f-5m9r-5jc2"},{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":"pkg:pypi/praisonai-platform","source":"PYSEC-2026-2933"}],"prev":{"headline":"praisonai-platform: Any workspace member can promote themselves or others to owner via PATCH /workspaces/{id}/members/{user_id}","id":"CVE-2026-47416"},"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":"partial"},"state":"PUBLISHED","updated":"2026-07-21","vendors":["MervinPraison"]},"summary":"Attackers can read and post comments on issues in other workspaces due to missing ownership checks, affecting PraisonAI Platform users.","url":"https://insights.sbomify.com/CVE-2026-47417/"}