CVE-2026-47399 is a high-severity object-level authorization vulnerability in PraisonAI Platform affecting versions prior to 0.1.4. Workspace-scoped REST routes for objects such as agents, projects, issues, and comments validate that the caller is a member of the workspace identified in the request URL, but the downstream service logic resolves target objects solely by their global UUID. The implementation does not verify that the resolved object actually belongs to the workspace referenced by the route. This creates an insecure direct object reference condition across workspace boundaries: an authenticated user in one workspace can invoke a workspace-scoped endpoint under a workspace they legitimately belong to while supplying the UUID of an object owned by a different workspace. The server then authorizes the request based on the attacker-controlled workspace context and performs the requested operation against the victim object, breaking tenant and workspace isolation.
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.
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.