Loading vulnerability…
Flowise versions before 3.1.3 contain a broken access-control vulnerability in the upsert-history API. The API returns server-wide upsert-history records rather than restricting results to the requesting user, tenant, workspace, or project. The returned records can include sensitive integration configuration, including Vector Store parameters, and response sizes may exceed 100 MB. The issue reflects missing or insufficient authorization enforcement and inadequate multi-tenant data 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.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Flowise vulnerability that could enable unauthorized access to protected functionality and sensitive information by bypassing application controls.
An information exposure vulnerability in Flowise caused by missing or insufficient authorization and tenant/workspace isolation in the GET /api/v1/upsert-history endpoint, allowing unauthorized access to server-wide upsert history and sensitive configuration data.
An authorization and tenant/workspace-isolation flaw in Flowise that permits exposure of server-wide upsert-history data and sensitive integration and infrastructure configuration details. Fixed in Flowise 3.1.3.
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.