Loading vulnerability…
CVE-2026-41267 is an improper mass assignment / JSON injection vulnerability in the Flowise Cloud account registration endpoint affecting versions prior to 3.1.0. During account creation, the endpoint improperly accepts attacker-supplied server-managed fields and nested objects instead of strictly enforcing an allowlist of client-settable properties. As a result, an unauthenticated attacker can submit crafted registration data that manipulates sensitive internal attributes such as ownership metadata, timestamps, organization association, and role mappings. In a multi-tenant deployment, this breaks intended trust boundaries by allowing client control over fields that should be assigned exclusively by the server.
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 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.