CVE-2026-130796: Flowise 3.1.3 through 3.1.4 MCP Server Token Disclosure via Public Chatflow Endpoint

Published Nov 17, 2026
·
Updated

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.

Affected Software

1 affected component
Flowise Flowise>=3.1.3<=3.1.4

Event History

Nov 17, 2026
CVE Published
via MITRE·07:47 PM
Data Sourced
via MITRE·07:47 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which Flowise versions should be prioritized for triage?

Flowise versions 3.1.3 through 3.1.4 are identified as affected.

2

Does an attacker need credentials or user interaction to exploit this issue?

No. The issue is described as exploitable by an unauthenticated attacker through the public chatflow endpoint, with no user interaction required.

3

What can an attacker do with a disclosed token?

The leaked MCP server bearer token can be used on the MCP route to invoke chatflows. This bypasses API key protection and can consume the chatflow owner's model quota.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203