Flowise versions prior to 3.1.2 expose chatflow configurations across all workspaces when the keyonly query parameter is omitted. An attacker possessing a valid API key from one workspace can trigger the /api/v1/chatflows/apikey/:apikey endpoint to retrieve not only the chatflows tied to that key but also all unprotected chatflows belonging to other workspaces. The disclosed data includes internal flow structure, system prompts, node settings, chatbot configuration, API settings, and credential identifiers. This vulnerability is classified as CWE‑863, a missing enforcement of a required feature or function, resulting in a confidentiality breach of sensitive configuration information. No arbitrary code execution or denial of service capability is present.

The flaw affects all Flowise deployments using versions earlier than 3.1.2, including the 3.0.x release line and earlier releases. Any installation of Flowise that has unprotected chatflows or that exposes the /api/v1/chatflows/apikey endpoint to users with API keys is susceptible.

The CVSS score of 5.3 indicates moderate severity. The exploitation requires possession of an existing API key from any workspace; no additional authentication is needed. The lack of a workspace filter makes the vulnerability trivial to exploit for users who obtain a key. EPSS data is unavailable, and the vulnerability has not been listed in CISA's KEV catalog, suggesting no known large‑scale active exploitation yet. Nevertheless, the ease of exploitation combined with the exposure of potentially sensitive configuration data warrants timely mitigation.