Loading vulnerability…
CVE-2026-70474 is an incorrect-authorization vulnerability in Flowise versions before 3.1.3. OAuth2 credential authorization, callback, and refresh handling retrieves credentials solely by their identifier without enforcing workspace ownership. In addition, the callback and refresh handlers are accessible without authentication. This breaks workspace isolation for OAuth2 credentials and permits unauthorized operations against credentials belonging to other workspaces.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Authentication and authorization flaw in Flowise OAuth mechanisms that could allow unauthorized access to application resources and functions.
A high-severity authorization flaw in Flowise OAuth2 credential endpoints prior to version 3.1.3. Credential lookup lacks workspace isolation, while callback and refresh handlers are exempted from authentication, enabling cross-workspace OAuth2 flow initiation and unauthenticated token overwrite or refresh for arbitrary credentials.
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.