Loading vulnerability…
Flowise versions earlier than 3.1.3 expose an OAuth2 credential-refresh API route without authentication because it is placed on the unauthenticated route whitelist. Given a valid stored credential identifier, the route decrypts the associated OAuth credential, submits its client secret and refresh token to the configured OAuth provider, and returns the resulting access token to the requester.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical unauthenticated access-token disclosure flaw in Flowise's OAuth2 credential-refresh endpoint. A remote attacker with a credential ID can retrieve refreshed OAuth access tokens for connected services and abuse refresh-token quotas. Fixed in Flowise 3.1.3.
An authentication bypass / information exposure vulnerability in Flowise's OAuth credential refresh endpoint that allows unauthenticated attackers with a credential ID to obtain refreshed access tokens for connected services.
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.