CVE-2026-130796
Deferred Deferred - Pending Action

Information Disclosure in Flowise AI Platform

Vulnerability report for CVE-2026-130796, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
FlowiseAI Flowise From 3.1.3 (inc) to 3.1.4 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-212 The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Flowise versions 3.1.3 to 3.1.4 have an information disclosure flaw. Unauthenticated attackers can access MCP server bearer tokens by querying the GET /api/v1/public-chatflows/:id endpoint. These tokens can then be used on the POST /api/v1/mcp/:chatflowId route to run chatflows, bypass API key restrictions, and consume the owner's model quota.

Detection Guidance

Check Flowise server logs for unusual GET requests to /api/v1/public-chatflows/:id endpoints. Monitor network traffic for POST requests to /api/v1/mcp/:chatflowId without prior authentication. Inspect bearer tokens in responses or requests to these endpoints.

Impact Analysis

If you use Flowise 3.1.3 or 3.1.4, attackers could steal MCP tokens and use your resources without permission. This may lead to unauthorized API calls, increased costs, and potential service disruption due to quota exhaustion.

Mitigation Strategies

Upgrade Flowise to a patched version beyond 3.1.4. Restrict access to the /api/v1/public-chatflows/:id and /api/v1/mcp/:chatflowId endpoints via firewall rules. Rotate all MCP server bearer tokens and API keys immediately.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130796. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...