CVE-2026-41279 Flowise: Unauthenticated TTS endpoint accepts arbitrary credential IDs — enables API credit abuse via stored credentials

High 8.2 Published 23 Apr 2026 Updated 23 Apr 2026

Unauthenticated users can abuse stored API credentials via the text-to-speech endpoint, leading to unauthorized API usage and potential financial loss.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2026-41279?

CVE-2026-41279 is a high-severity missing authorization vulnerability in Flowiseai Flowise, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-639

Which versions are affected by CVE-2026-41279?

2 open source packages ship an affected version, including flowise. It affects 1 product.

Package	Affected	Fixed in
`flowise` npm	All versions	`3.1.0`
`flowise` npm	All versions	`3.1.0`

Products include Flowiseai Flowise.

How do I fix CVE-2026-41279?

Upgrade flowise to 3.1.0 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-41279 being exploited?

There is no known exploitation of CVE-2026-41279 in the wild and no public exploit code.

All Flowiseai Flowise vulnerabilities

Sources

Also known as GHSA-5fw2-mwhh-9947.