CVE-2026-41279: Flowise: Unauthenticated TTS endpoint accepts arbitrary credential IDs — enables API credit abuse via stored credentials
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, the text-to-speech generation endpoint (POST /api/v1/text-to-speech/generate) is whitelisted (no auth) and accepts a credentialId directly in the request body. When called without a chatflowId, the endpoint uses the provided credentialId to decrypt the stored credential (e.g., OpenAI or ElevenLabs API key) and generate speech. This vulnerability is fixed in 3.1.0.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41279?
CVE-2026-41279 has a high severity rating due to its potential for API credit abuse through unauthorized access.
How do I fix CVE-2026-41279?
To fix CVE-2026-41279, you should upgrade to Flowise version 3.1.0 or later.
What is the impact of CVE-2026-41279?
The impact of CVE-2026-41279 includes potential abuse of API credits, leading to unauthorized usage and financial implications.
Who is affected by CVE-2026-41279?
Users of Flowise versions prior to 3.1.0 are affected by CVE-2026-41279.
What type of vulnerability is CVE-2026-41279?
CVE-2026-41279 is an unauthenticated API vulnerability that allows for arbitrary credential ID acceptance.