
1/ Running Flowise? Two new CVEs dropped Nov 17, and there's no patch coming. Flowise hit end of life on Aug 31 and the repo is archived. 2/ CVE-2026-130796 (CVSS 8.2): on 3.1.3–3.1.4, GET /api/v1/public-chatflows/:id hands the chatflow's MCP server bearer token to anyone. With it they can run your chatflow over /api/v1/mcp/ without the API key, on your model bill. 3/ CVE-2026-130615 (7.1): the SSRF deny list doesn't pin DNS, so the Playwright/Puppeteer loaders can be pointed at 169.254.169.254 or internal hosts with a rebinding domain. 4/ What to do now: turn off MCP server access on public chatflows (or make them private), rotate those MCP tokens, block egress to cloud metadata, and plan a move off Flowise. Check + fix steps: https://vibevulns.com/issues/flowise-mcp-server-token-leak-public-chatflows-and-dns-rebinding-ssrf-cve-2026-130796-130615/ 5/ Also this week: Kubeshark's MCP download_file tool wrote to any path the agent picked (think ~/.ssh/authorized_keys via prompt injection). Fixed in 53.4.0. https://vibevulns.com/issues/cve-2026-129235-kubeshark-mcp-download-file-arbitrary-file-write-via-prompt-injection-fixed-53-4-0/



