Flowise: Incomplete Credential Redaction Exposes Secrets via API
GHSA-rwrp-9823-p2xq · published 2026-08-04 · updated 2026-09-02
- Severity
- Medium
- CVSS score
- 6.5
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 3.1.3
Database credential theft: MongoDB, PostgreSQL, Redis, MySQL connection URLs with embedded passwords are returned in full plaintext. An attacker can use these to directly access production databases. Cloud service account compromise: Google service account JSON with RSA private keys is returned in plaintext, enabling full impersonation of the service account across Google Cloud. AWS key exposure: AWS Access Key IDs stored in string-type fields are exposed, enabling enumeration of active AWS credentials. Lateral movement: Stolen credentials enable pivoting from the Flowise instance to connected cloud services, databases, and APIs.
Upgrade flowise to 3.1.3 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. Apply redactCredentialWithPasswordType() to all sensitive credential fields, not just those typed as password. Any field containing secrets (connection strings, JSON credentials, access keys) should be redacted. 2. Consider never returning plainDataObj in API responses. The UI should use masked previews (e.g., mongodb+srv://admin:****@cluster0...) instead of full values. 3. Re-type sensitive credential fields from string to password in component credential definitions to ensure they are covered by the existing redaction logic. 4. Add a separate secret: true flag to credential field definitions to explicitly mark sensitive fields regardless of their input type.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.2 | 3.1.3 |
- 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.