CVE-2026-130796

Flowise 3.1.3 through 3.1.4 MCP Server Token Disclosure via Public Chatflow Endpoint

Published Nov 17, 2026 CVSS 4.0 · 8.8 High EPSS n/a KEV · Not listed
Description
Flowise 3.1.3 through 3.1.4 contains an information disclosure vulnerability that allows unauthenticated attackers to read MCP server bearer tokens via the GET /api/v1/public-chatflows/:id handler. Attackers can use the leaked mcpServerConfig token on the POST /api/v1/mcp/:chatflowId route to invoke chatflows, bypassing API key protection and consuming the owner's model quota.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor patch or upgrade to a Flowise release that fixes the token disclosure issue.
  • If an immediate upgrade is not possible, restrict the /api/v1/public-chatflows endpoint to authenticated users only, preventing unauthenticated access.
  • Modify the configuration or code to remove exposure of the mcpServerConfig token so that it is no longer returned in public responses.
  • Implement monitoring of API usage to detect abnormal model quota consumption that may indicate abuse of leaked tokens.

Generated by OpenCVE AI on November 17, 2026 at 21:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description Flowise 3.1.3 through 3.1.4 contains an information disclosure vulnerability that allows unauthenticated attackers to read MCP server bearer tokens via the GET /api/v1/public-chatflows/:id handler. Attackers can use the leaked mcpServerConfig token on the POST /api/v1/mcp/:chatflowId route to invoke chatflows, bypassing API key protection and consuming the owner's model quota.
Title Flowise 3.1.3 through 3.1.4 MCP Server Token Disclosure via Public Chatflow Endpoint
First Time appeared Flowiseai
Flowiseai flowise
Weaknesses CWE-212
CPEs cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
Vendors & Products Flowiseai
Flowiseai flowise
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N'}

cvssV4_0

{'score': 8.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-212

    Improper Removal of Sensitive Information Before Storage or Transfer

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 17, 2026, 7:47 PM
Reserved
Nov 17, 2026, 3:44 PM
Status
Deferred
Published
Nov 17, 2026, 8:17 PM
Modified
Nov 17, 2026, 8:17 PM