Flowise before 3.1.4 fails to validate chatflow visibility in the unauthenticated text-to-speech endpoint, allowing attackers to abuse private chatflow TTS credentials. Unauthenticated attackers can generate unlimited text-to-speech audio using stored OpenAI or ElevenLabs API keys by providing a valid chatflow UUID, incurring costs on the chatflow owner's account.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-8gj2-2cvc-6xx7 Exploit, Mitigation, Vendor Advisory
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-8gj2-2cvc-6xx7 Exploit, Mitigation, 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 6.3 · flowiseaiNVD modified 2026-10-23 18:10
Affected (CPE criteria) 1
cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
References 3
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-8gj2-2cvc-6xx7 Exploit, Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/flowise-before-credential-abuse-via-text-to-speech Third Party Advisory
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-8gj2-2cvc-6xx7 Exploit, Mitigation, Vendor Advisory