FlowiseAI Exposes Basic Auth Credentials via API
CVE-2026-46440 · GHSA-php6-83fg-gw3g · published 2026-05-14 · updated 2026-06-09
- Severity
- High
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- 0.23%
- Fixed in
- 3.1.2
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
Credential brute-forcing - attackers can attempt unlimited username/password combinations against the basic auth system. Successful attacks grant access to the application.
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.
1) Implement rate limiting on this endpoint, 2) Use constant-time comparison to prevent timing attacks, 3) Consider using hashed comparison, 4) Return generic error messages, 5) Add logging for failed attempts.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.1 | 3.1.2 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
- HighWorkspace dotenv files could override provider credentialsopenclaw
- 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.