Is CVE-2026-41279 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41279 being exploited in the wild.

How severe is CVE-2026-41279?

High severity, with a CVSS score of 7.5, published 23 April 2026.

Which products and versions are affected?

flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.

Is there a fix for CVE-2026-41279?

Yes. flowise (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41279 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-41279?

Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

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

Q: Which products and versions are affected?

flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.

Q: Is there a fix for CVE-2026-41279?

Yes. flowise (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-41279 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-41279?

Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41279 · Severity: high · CVSS 7.5 · Published 2026-04-23

Flowise is a visual AI agent builder that integrates with external APIs like OpenAI and ElevenLabs for text-to-speech generation. The text-to-speech endpoint is publicly accessible without authentication and accepts arbitrary stored credential IDs from client requests, allowing attackers to use victim API keys to generate speech content and exhaust API credits at the victim's expense.

Technologies: FlowiseAI Flowise, flowise (npm). Vendors: FlowiseAI, npm.

Quick answers

Is CVE-2026-41279 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41279 being exploited in the wild.
How severe is CVE-2026-41279?: High severity, with a CVSS score of 7.5, published 23 April 2026.
Which products and versions are affected?: flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.
Is there a fix for CVE-2026-41279?: Yes. flowise (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41279 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-41279?: Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

flowise (npm): upgrade to 3.1.0 or later
```
npm install flowise@3.1.0
```

Technical details

The vulnerability exists in the POST /api/v1/text-to-speech/generate endpoint (packages/server/src/controllers/text-to-speech/index.ts:58-64), which is whitelisted in WHITELIST_URLS and therefore bypasses authentication. When no chatflowId is provided, the endpoint accepts a credentialId directly from the request body and uses it to decrypt and load stored API credentials. An attacker can send a POST request with an arbitrary credentialId to call the endpoint without authentication, and the server will process the request and decrypt the victim's stored credential. The endpoint does not validate that the credential ID belongs to the requesting user or their chatflow. By repeatedly calling this endpoint with different credential IDs discovered via other means (credential enumeration), an attacker can consume victim API credits. The fix removes the endpoint from the whitelist or validates that any credentialId matches the chatflow's TTS configuration. Patched in version 3.1.0.

Affected products

FlowiseAI Flowise <= 3.0.13

Identifiers

CVE-2026-41279
GHSA-5fw2-mwhh-9947

Timeline

2026-04-17: disclosed: Advisory published
2026-04-15: patched: Patched in version 3.1.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.