Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, the GET /api/v1/public-chatflows/:id endpoint returns the full chatflow object without sanitization for public chatflows. Docker validation revealed this is worse than initially assessed: the sanitizeFlowDataForPublicEndpoint function does NOT exist in the released v3.0.13 Docker image. Both public-chatflows AND public-chatbotConfig return completely raw flowData including credential IDs, plaintext API keys, and password-type fields. This vulnerability is fixed in 3.1.0.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-w47f-j8rh-wx87 Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.7 · flowiseaiNVD modified 2026-10-26 21:10
Affected (CPE criteria) 1
cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
References 1
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-w47f-j8rh-wx87 Exploit, Vendor Advisory