CVE-2026-47417 is an insecure direct object reference vulnerability in PraisonAI Platform affecting versions prior to 0.1.4. The flaw is in the issue comment endpoints, which authorize requests by checking only whether the caller is a member of the workspace identified in the URL. The implementation then creates or lists comments using the supplied issue identifier without verifying that the referenced issue actually belongs to that workspace. Because object-level authorization is not enforced on the issue-to-workspace relationship, an authenticated user with membership in one workspace can access comment data associated with issues in other workspaces and can also submit new comments to those cross-workspace issues.
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.