CVE-2026-70636 is an authentication and authorization bypass vulnerability in Flowise through version 3.1.4 affecting the OAuth2 credential refresh functionality. The flaw stems from prefix-based whitelist matching in the authentication middleware, where the OAuth2 credential refresh route is treated as globally whitelisted and excluded from normal API key and JWT enforcement. By sending a crafted POST request to the OAuth2 credential refresh route with a trailing credential identifier, an unauthenticated attacker can reach the refresh handler without passing authentication checks. The handler then loads credentials by identifier, decrypts the stored OAuth material, performs a token refresh operation, and updates the stored credential record without verifying caller identity, workspace ownership, or role-based authorization. This results in unauthorized cross-workspace manipulation of OAuth credential state and is described as a bypass of the earlier CVE-2026-41273 remediation.
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.
6 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.