{"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-48169 exists.","fix":"Upgrade praisonai-platform to 0.1.4 or later.","what":"CVE-2026-48169 is a high-severity missing authorization vulnerability in MervinPraison praisonai-platform, published on 7 Aug 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-48169 and fix it if it is affected.\n\nWhat it is: CVE-2026-48169 is a high-severity missing authorization vulnerability in MervinPraison praisonai-platform, published on 7 Aug 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-48169 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-48169/ (Markdown: https://insights.sbomify.com/CVE-2026-48169/index.md)","id":"CVE-2026-48169","markdown":"https://insights.sbomify.com/CVE-2026-48169/index.md","name":"CVE-2026-48169","record":{"aliases":["GHSA-gv23-xrm3-8c62","PYSEC-2026-2935"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"PraisonAI Platform API","requires_auth":"low_privilege","summary":"Authenticated users can access and modify resources in any workspace and escalate privileges to owner due to missing authorization checks in the service layer.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"PraisonAI is a multi-agent teams system. Versions prior to 0.1.4 of the PraisonAI Platform API have two authorization failures that together break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, so any authenticated user can read, modify, and delete resources in any workspace just by swapping UUIDs in their API requests. On top of that, every member management endpoint (add, update role, remove) only requires `min_role=\"member\"`, which lets any workspace member promote themselves to owner and kick out the original owner. A low-privilege member of one workspace can steal data from every other workspace and take over any workspace they belong to. Both issues come from the same gap: the route layer pulls `workspace_id` from the URL and verifies membership, but the service layer ignores the workspace scope for resource lookups and ignores the caller's role level for member operations. The `require_workspace_member()` dependency does its job correctly. The problem is that the service layer doesn't use the information it provides. Version 0.1.4 of the PraisonAI Platform API patch 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 has Cross-Workspace IDOR and Privilege Escalation via Platform API","id":"CVE-2026-48169","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":"scimPatch vulnerable to prototype pollution via unfiltered keys in patch","id":"CVE-2026-48170"},"packages":[{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":null,"source":"GHSA-gv23-xrm3-8c62"},{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":"pkg:pypi/praisonai-platform","source":"GHSA-gv23-xrm3-8c62"},{"ecosystem":"PyPI","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"praisonai-platform","purl":"pkg:pypi/praisonai-platform","source":"PYSEC-2026-2935"}],"prev":{"headline":"PraisonAI: GitHub Actions Claude workflow command injection via unquoted PR branch name","id":"CVE-2026-48168"},"products":["praisonai-platform"],"published":"2026-08-07","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-11","vendors":["MervinPraison"]},"summary":"Authenticated users can access and modify resources in any workspace and escalate privileges to owner due to missing authorization checks in the service layer.","url":"https://insights.sbomify.com/CVE-2026-48169/"}