Flowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected service
CVE-2026-70478 · GHSA-qgvm-j2hm-6m38 · published 2026-08-04
- Severity
- Critical
- CVSS score
- 9.2
- Chance of exploitation (EPSS)
- 0.61%
- Fixed in
- 3.1.3
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
OAuth2 access token theft for any connected service Full access to the victim's third-party accounts (Google, Microsoft, GitHub, etc.) Client secret transmitted to OAuth provider during refresh Can also be used for DoS by exhausting refresh token quota
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.
Remove the refresh endpoint from WHITELIST_URLS and require authentication: ---
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.2 | 3.1.3 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
- HighWorkspace dotenv files could override provider credentialsopenclaw
- 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.