Flowise: unauthenticated MCP server bearer-token leak via /api/v1/public-chatflows (CVE-2026-130796) and DNS-rebinding SSRF in Playwright/Puppeteer loaders (CVE-2026-130615); no fix coming
Two new Flowise CVEs were published on 17 November 2026. In Flowise 3.1.3 through 3.1.4, GET /api/v1/public-chatflows/:id returns a chatflow's MCP server bearer token to unauthenticated callers, who can then call POST /api/v1/mcp/:chatflowId to run the chatflow without its API key and on the owner's model quota. In Flowise through 3.1.4, the SSRF deny list in checkDenyList() doesn't pin DNS, so a chatflow using the Playwright or Puppeteer document loader with a DNS-rebinding domain can make headless Chromium fetch internal or cloud-metadata endpoints. Flowise was wound down (repository archived, end of life 31 August 2026), so no patched release is expected.
What it is
CVE-2026-130796 (CWE-212, credit George Chen): the public-chatflow handler in packages/server/src/controllers/chatflows/index.ts returns the stored chatflow entity including mcpServerConfig, whose token is the bearer credential the MCP endpoint (services/mcp-server) accepts. Affected: Flowise >= 3.1.3, <= 3.1.4.
CVE-2026-130615 (CWE-367 TOCTOU, credit N3st1c): checkDenyList() in packages/components/src/httpSecurity.ts resolves and checks the hostname, but the Playwright and Puppeteer loaders then let Chromium resolve it again. A rebinding domain passes the check and then points at 127.0.0.1, internal hosts or 169.254.169.254, and the page body comes back as document content. Needs an authenticated user who can configure a chatflow. Affected: Flowise <= 3.1.4.
Flowise announced a code freeze on 29 July 2026, archived the GitHub repository on 10 August and reached end of life on 31 August 2026; the VulnCheck records link to that sunset notice.
How to check
- Run your Flowise version check (Settings or package.json); 3.1.3 and 3.1.4 are affected by both, anything up to 3.1.4 by the SSRF.
- Without credentials, request /api/v1/public-chatflows/<id> for a public chatflow that has MCP server access enabled and see whether the response contains mcpServerConfig with a token.
How to fix
- Plan a migration off Flowise or onto a maintained fork that has fixed these issues; the upstream project will not ship patches.
- Until then, turn off MCP server access on public chatflows (or make the chatflows private) and rotate MCP server tokens that were exposed.
- Remove or restrict Playwright/Puppeteer loaders, limit chatflow editing to trusted users, and block the Flowise host from 169.254.169.254 and internal networks with egress rules.
# prints 1 or more if the public endpoint exposes MCP server config
curl -s https://FLOWISE_HOST/api/v1/public-chatflows/CHATFLOW_ID | grep -c mcpServerConfig Sources
- criticalCVE-2026-73487: Flowise CSV and Airtable agents can be prompt-injected into leaking data and SSRF
- criticalCVE-2026-73483: Flowise custom functions could escape the sandbox through puppeteer.launch()
- highCVE-2026-119978: Flowise through 3.1.4 lets logged-in users escape the custom-function sandbox and run OS commands when ALLOW_BUILTIN_DEP=true