CVE-2026-130796

8.2High

Published 17 Nov 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite

8.2CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
High impact on confidentiality
Weakness
CWE-212

What an attacker gets

Unauthenticated attackers can steal MCP server bearer tokens to hijack chatflows and drain your model quota. They only need network access to the Flowise API endpoint.

Root cause

The /api/v1/public-chatflows/:id endpoint incorrectly exposes sensitive MCP server configuration tokens in its response.

Affected versions

Flowise 3.1.3 through 3.1.4

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Fix & remediation

Upgrade to a version beyond 3.1.4. If you cannot upgrade immediately, restrict network access to the Flowise API to trusted internal IP addresses only.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-130796