Loading vulnerability…
CVE-2026-47407 is a critical authorization flaw in PraisonAI Platform affecting versions prior to 0.1.4. Workspace-scoped API routes under the workspace URL namespace rely on a membership check that validates only whether the caller belongs to the workspace identifier supplied in the URL prefix. The affected route handlers then retrieve nested resources such as agents, issues, projects, labels, comments, and dependencies by primary key alone, without verifying that the resource's actual workspace association matches the workspace identifier in the request path. This creates a cross-tenant insecure direct object reference condition in which a user can supply a workspace they legitimately belong to in the URL while referencing another workspace's resource identifier, resulting in unauthorized read, update, or delete access to data outside their tenant boundary. A second authorization defect affects workspace member-management and administrative routes, where operations inherit a default minimum role of member rather than enforcing the intended role hierarchy. As a result, ordinary workspace members can perform privileged actions including changing roles, removing members, modifying workspace settings, and deleting the workspace. The issue is especially exposed in deployments where self-registration is enabled without email verification and the service is reachable over the network using its default bind configuration. Version 0.1.4 corrects the tenancy validation and role-enforcement logic.
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.
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.
3 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.