Flowise: Cross-Workspace OAuth2 Credential Metadata Leak
CVE-2026-70474 · GHSA-wch5-xp77-fxg4 · published 2026-08-04
- Severity
- High
- CVSS score
- 7.6
- Chance of exploitation (EPSS)
- 0.48%
- Fixed in
- 3.1.3
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
| Vector | Auth Required | Impact | |--------|--------------|--------| | Credential metadata leak via /authorize | Low (any session) | Exposes clientid, scope, redirecturi from any workspace's credential | | Token injection via /callback | None | Overwrite any credential's stored OAuth2 tokens with attacker-controlled values | | Token theft via /refresh | None | Obtain a fresh accesstoken for any credential's connected service (Microsoft 365, Google, etc.) | Chained impact:** An attacker who obtains a single credential UUID (via IDOR, log exposure, or brute-force of UUIDs) can silently refresh and steal OAuth2 access tokens for external services like Microsoft Graph, Google Workspace, or any…
Upgrade flowise to 3.1.3 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
1. Add workspaceId to all credential lookups in the OAuth2 routes, matching the pattern already used in services/credentials/index.ts:130-132: 2. Remove /callback and /refresh from WHITELISTURLS or implement a signed, time-limited state token that authenticates the callback without a session. 3. Replace the state parameter with a cryptographically random nonce bound to the user's session (see also Finding 8). 4. Do not return accesstoken in the /refresh response body. The token should only be stored server-side in the encrypted credential data, never sent to the caller. ---
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.2 | 3.1.3 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- CriticalFlowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypassflowise, flowise-components
- CriticalCross-IdP account takeover via email-only SSO matchingflowise
- CriticalINVITED users auto-promoted via SSO email match (invite-token bypass)flowise
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.