Flowise: Hardcoded CORS wildcard on TTS endpoint enables cross-origin credential abuse from any webpage
GHSA-m837-xvxr-vqwg · published 2026-05-20
- Severity
- Medium
- CVSS score
- 6.9
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 3.1.2
Cross-origin credential abuse — any webpage can trigger TTS using stored credentials Bypasses the server's CORS policy (getCorsOptions()) which is otherwise restrictive by default Combined with Finding 3 (TTS credential abuse), enables drive-by credential abuse via malicious webpages
Upgrade flowise to 3.1.2 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Remove the hardcoded CORS wildcard and let the server's CORS middleware handle the headers: ---
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.1 | 3.1.2 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- CriticalFlowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypassflowise, flowise-components
- CriticalCross-IdP account takeover via email-only SSO matchingflowise
- CriticalINVITED users auto-promoted via SSO email match (invite-token bypass)flowise
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.