Flowise: Cross-Workspace Chatflow Disclosure via chatflows/apikey Endpoint Returns All Unprotected…
Flowise
More for Flowise RSS feed for Flowise
- Severity
- High, CVSS 7.7
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- Record
- CVE-2026-56268
- Affects
- Flowise
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- June 22, 2026
- Source last modified
- October 25, 2026
Description
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.
Description quoted from the NVD record.
Who is affected
Flowise is a tool for building apps and chatbots that use AI language models. This flaw affects versions before 3.1.2. It sits in the part of Flowise that lists chat workflows (called chatflows) linked to an access key. By default, someone with a valid access key for one workspace can also see every chatflow in other workspaces that has no access key assigned. They could read the full setup of those chatflows, including the instructions given to the AI, other configuration details and references to stored login credentials. This flaw is rated High.
What to do
- If someone in your organization installed or runs Flowise, ask that person to check which version of Flowise is in use.
- Have them update Flowise to version
3.1.2or later, which fixes this flaw. Any version before3.1.2is affected. - If an IT provider or vendor runs Flowise for your organization, send them this advisory and ask when the update will be done.
- Give this update priority if your Flowise setup has more than one workspace, since the flaw lets anyone holding an access key for one workspace see chatflows from others.
Analysis written from the source record as of October 25, 2026 and reviewed before publishing.