Auth bypass in Flowise
CVE-2026-56268
Flowise before 3.1.2 contains an information disclosure vulnerability in the /api/v1/chatflows/apikey/:apikey endpoint. When the keyonly query parameter is omitted (the default), the endpoint returns not only the chatflows bound to the supplied API key but also all chatflows across every workspace that have no API key assigned, because the underlying query lacks any workspace filter. An attacker with a valid API key for one workspace can therefore retrieve the full ChatFlow configuration (including flowData with system prompts and node configurations, chatbotConfig, apiConfig, and credential IDs) of unprotected chatflows belonging to other workspaces.
Vulnerability class: Broken Access Control
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.7 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.004, 33.7th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Flowise — versions 0, 3.1.2
- Flowiseai Flowise
Weakness classification (CWE)
References
- GitHub Security Advisory (GHSA-c2c9-mfw7-p8hw) (vendor-advisory, Exploit, Third Party Advisory)
- VulnCheck Advisory: Flowise - Cross-Workspace Information Disclosure via chatflows/apikey Endpoint (Third Party Advisory, third-party-advisory)