Technical impact
The vulnerability in Flowise 3.1.3 and 3.1.4 allows attackers to read MCP server bearer tokens through the public chatflow endpoint. Because the token is exposed, an attacker can later use it to invoke chatflows without the API key, resulting in unauthorized consumption of the owner's model quota. This flaw is a classic case of information disclosure (CWE-212) that can lead to resource exhaustion and credential misuse.
Affected Systems
Flowise AI’s Flowise platform versions 3.1.3 through 3.1.4 are affected. The vulnerability surfaces in the GET /api/v1/public-chatflows/:id handler, which is publicly accessible without authentication. The leaked token is then supplied to the POST /api/v1/mcp/:chatflowId route to bypass any API key checks.
Risk and Exploitability
The CVSS score of 8.8 highlights a high severity design flaw. Although the EPSS score is unavailable, the lack of mitigation and the straightforward nature of the exploit point to a significant potential for exploitation. The vulnerability is not listed in the CISA KEV catalog, but its impact—unauthenticated token disclosure—makes a timely patch essential. A likely attack vector would involve sending a simple HTTP GET request to the public endpoint, extracting the bearer token from the response, and then performing POST requests to hijack chatflow execution. The ease of this attack path, combined with a high CVSS score, underscores the urgency of remediation.