CVE-2026-56268: Flowise - Cross-Workspace Information Disclosure via chatflows/apikey Endpoint
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Flowiseto a version that resolves this vulnerability.Fixed in 3.1.2 - Configuration
Ensure the client calls the endpoint with the keyonly query parameter set (do not omit it) to prevent disclosure of chatflows across other workspaces.
Flowise /api/v1/chatflows/apikey/:apikey endpoint keyonly query parameter = required
Event History
Frequently Asked Questions
What is the severity of CVE-2026-56268?
CVE-2026-56268 has a medium severity score of 5.3.
What is CVE-2026-56268 about?
CVE-2026-56268 describes an information disclosure vulnerability in the Flowise API that exposes chatflows across all workspaces.
How do I fix CVE-2026-56268?
To fix CVE-2026-56268, upgrade to Flowise version 3.1.2 or later where the vulnerability is patched.
What is the risk associated with CVE-2026-56268?
The risk associated with CVE-2026-56268 is categorized as medium, with a risk score of 44.
How can CVE-2026-56268 affect my organization?
CVE-2026-56268 can lead to unauthorized access to sensitive chatflows across different workspaces, potentially compromising data security.