CVE-2026-70474: Incorrect Authorization and Missing Authentication in Flowise OAuth2 Credential Endpoints
Vulnerability ID: CVE-2026-70474
CVSS Score: 7.6
Published: 2026-08-04
A critical authorization flaw exists in Flowise, a popular drag-and-drop orchestrator for building customized Large Language Model flows. Prior to version 3.1.3, multiple OAuth2 credential endpoints do not filter database lookups by the requesting entity's workspace context. This omission, combined with the exclusion of several endpoints from the global authentication pipeline, permits unauthenticated remote actors to access, manipulate, or steal access tokens linked to external service integrations.
TL;DR
Unauthenticated remote attackers can exfiltrate active third-party access tokens, inject rogue OAuth2 states, or access cross-workspace metadata due to missing workspace isolation and overly permissive API routing whitelists in Flowise < 3.1.3.
Technical Details
- CWE ID: CWE-863 (Incorrect Authorization)
- Attack Vector: Network (AV:N)
- CVSS Score: 7.6 (High)
- Exploit Status: PoC / Publicly Documented
- KEV Status: Not Listed
- Impact: Unauthenticated Token Theft & Injection
Affected Systems
- Flowise (npm package 'flowise')
Mitigation Strategies
- Upgrade Flowise to version 3.1.3 or later
- Deploy Flowise behind a VPN or Zero-Trust Network Access (ZTNA) gateway
- Configure WAF rules to block external access to '/api/v1/oauth2-credential/refresh/' and '/api/v1/oauth2-credential/callback' paths
Remediation Steps:
- Verify the installed version of Flowise in package.json or system headers
- Execute 'npm install flowise@3.1.3' or update container images to 'flowiseai/flowise:3.1.3' or newer
- Rotate external OAuth2 client secrets and existing authorization tokens linked to Flowise database records
References
Read the full report for CVE-2026-70474 on our website for more details including interactive diagrams and full exploit analysis.
Top comments (0)