Prior to version 3.1.0, Flowise’s public chatflow API endpoint (GET /api/v1/public-chatflows/:id) returned the entire chatflow object without removing sensitive information. As a result, the response included credential IDs, plaintext API keys, and password‑type fields. This flaw can lead to the accidental disclosure of authentication secrets and other confidential data to anyone who can query a public chatflow ID.

The vulnerability affects the FlowiseAI Flowise product for all releases older than version 3.1.0. It applies to both the standard and Dockerized distributions, including the v3.0.13 Docker image, which lacks the sanitization function. Users running these older builds are exposed regardless of whether the public-chatflow endpoint is enabled via configuration.

The CVSS score of 8.7 reflect a high severity risk of sensitive data exposure. The EPSS score of less than 1% indicates that the probability of active exploitation is currently low, and the flaw is not yet listed in the CISA KEV catalog. The attack vector is remote over the network; an attacker only needs to know or discover a public chatflow identifier to retrieve the raw data. The lack of sanitization in the deployed image makes the data easily retrievable without additional privileges, so the risk primarily concerns confidentiality loss for credentials stored within the chatflow definitions.