AI Stack Alert High CVE-2026-130796 For CISO, SOC / IR, AppSec, AI Eng AI-assisted
Flowise 3.1.3-3.1.4 leaks MCP server bearer tokens via public-chatflows endpoint (CVE-2026-130796)
Flowise versions 3.1.3 through 3.1.4 contain an information disclosure vulnerability. Unauthenticated attackers can read MCP server bearer tokens through the GET /api/v1/public-chatflows/:id handler. The leaked token can be used on the POST /api/v1/mcp/:chatflowId route to invoke chatflows, bypassing API key protection.
Why it matters
Exposed Flowise deployments let unauthenticated attackers bypass API key protection and consume the owner's model quota. The reported CVSS base score is 8.8.
Do this
- Upgrade Flowise to a version later than 3.1.4 once a fixed release is confirmed in the vendor advisory.
- Review web server and proxy logs for unauthenticated GET requests to /api/v1/public-chatflows/ and POST requests to /api/v1/mcp/.
- Rotate MCP server bearer tokens and API keys for any chatflow that was publicly accessible on affected versions.
- Restrict or disable public chatflow access where it is not required, and monitor model API usage for unexpected spikes.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 8.8CVSS
- NoPublic PoC
- 36/100Priority
- 80%Confidence
Evidence
“Flowise 3.1.3 through 3.1.4 contains an information disclosure vulnerability that allows unauthenticated attackers to read MCP server bearer tokens”
“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.”
Sources
Affected / related
Flowise, MCP server bearer token disclosure
Published 2026-11-17 20:17 UTC · updated 2026-11-17 22:35 UTC · AI-assisted summary, checked against quoted sources · How we score