CVE-2026-47405 is a broken access control vulnerability in PraisonAI Platform, the platform layer for the PraisonAI multi-agent teams system. In versions prior to 0.1.4, privileged workspace-management routes rely on the shared authorization dependency require_workspace_member(...) without enforcing administrative role requirements. Because that dependency defaults to min_role="member", routes intended for admin or owner users are exposed to ordinary authenticated workspace members. This allows a low-privilege member within a workspace to perform unauthorized administrative actions, including promoting their own role to owner, modifying other users' roles, adding additional privileged users, and removing legitimate members. The flaw is a vertical privilege escalation caused by missing authorization on sensitive role- and membership-management operations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
owner or admin, alter other members' privileges, remove legitimate owners or members, fully seize control of workspace membership, and carry out destructive workspace operations. The resulting impact is high across confidentiality, integrity, and availability because the attacker can access and manipulate workspace resources and disrupt or lock out legitimate administration.If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.