Flowise's Critical Flaw Lets Anyone Steal Live OAuth Tokens Without Logging In
A high-severity flaw in Flowise lets anyone on the internet mint OAuth access tokens from public chatflows without authentication. Patch is out.
Takeaways
- Flowise CVE-2026-41273 lets unauthenticated attackers steal OAuth tokens from public chatflows. Advisory
- Fixed in Flowise 3.1.0; versions 3.0.13 and earlier are vulnerable, CVSS 7.7 High.
- Two whitelisted endpoints chain: public-chatbotConfig leaks credential IDs, oauth2-credential/refresh mints tokens.
- Bonus SSRF via user-controlled accessTokenUrl exfiltrates client_id, client_secret, and refresh_token to attacker servers.
- Follows CVE-2025-58434 password-reset takeover (CVSS 9.8) and a separate SSO client-secret disclosure bug.
- Mitigation: upgrade immediately, rotate every OAuth credential, audit third-party API logs for abuse.
A newly disclosed vulnerability in Flowise, the popular visual builder for LLM agents with over 52,000 GitHub stars, lets an unauthenticated attacker walk away with live OAuth 2.0 access tokens for any third-party service wired into a public chatflow. Think Gmail, Google Drive, or any provider whose credentials you plugged into the drag-and-drop canvas.
Tracked as CVE-2026-41273 and rated High with a CVSS score of 7.7, the flaw affects Flowise prior to version 3.1.0. If you self-host Flowise and have ever exposed a public chatbot or embed widget to the internet, this one is worth paying attention to.
Two innocent endpoints, one token heist
The vulnerability lives at the intersection of two design choices that are individually reasonable and collectively catastrophic. Flowise allows public chatflows to be accessed by unauthenticated end users via public URLs or embedded widgets, so chatflowId values are intentionally exposed to unauthenticated clients and must not be treated as secrets. Fine on its own.
The trouble begins with a specific endpoint. GET /api/v1/public-chatbotConfig/<chatflowId> returns internal flowData without authentication, and that flowData includes workflow node definitions containing OAuth credential identifiers. A second endpoint completes the chain: the authentication middleware treats