Is CVE-2026-73603 exploited in the wild?

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

How severe is CVE-2026-73603?

Medium severity, with a CVSS score of 5.3, published 13 August 2026.

Which products and versions are affected?

flowise (npm) SEMVER:introduced=0,fixed=3.1.4.

Is there a fix for CVE-2026-73603?

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

How is CVE-2026-73603 attacked?

It is attacked over the network.

Am I affected by CVE-2026-73603?

Check whether you run 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-73603: Flowise text-to-speech endpoint credential abuse via unauthenticated access

CVE-2026-73603 · Severity: medium · CVSS 5.3 · Published 2026-08-13

Flowise is an open-source platform for building conversational AI applications. The text-to-speech endpoint can be accessed without authentication and fails to verify whether a chatflow is private, allowing attackers to abuse stored TTS API credentials (OpenAI, ElevenLabs) belonging to other users. An attacker who discovers a chatflow ID can generate unlimited audio at the victim's cost, potentially causing significant financial damage and service disruption.

Technologies: flowise (npm). Vendors: npm.

Quick answers

Is CVE-2026-73603 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73603 being exploited in the wild.
How severe is CVE-2026-73603?: Medium severity, with a CVSS score of 5.3, published 13 August 2026.
Which products and versions are affected?: flowise (npm) SEMVER:introduced=0,fixed=3.1.4.
Is there a fix for CVE-2026-73603?: Yes. flowise (npm): upgrade to 3.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73603 attacked?: It is attacked over the network.
Am I affected by CVE-2026-73603?: Check whether you run 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.4 or later
```
npm install flowise@3.1.4
```

Technical details

The vulnerability is a broken access control issue in the /api/v1/text-to-speech/generate endpoint, which is whitelisted to require no authentication. When an unauthenticated request provides a chatflowId, the controller retrieves the chatflow without validating workspace scope or the isPublic flag. The getChatflowById function fetches any chatflow by ID when workspaceId is undefined, and the controller then extracts the TTS provider credentials (API keys) from the retrieved chatflow's configuration and uses them to make API calls on behalf of the attacker. An attacker with knowledge of a valid chatflow UUID can invoke the endpoint with arbitrary text to generate audio using the target chatflow's credentials, incurring costs and potentially exhausting API quotas. The vulnerability affects chatflows of any visibility level, including those explicitly marked private. A patch is available in version 3.1.4 that adds an isPublic check before allowing unauthenticated TTS generation.

Affected products

Flowise Flowise <= 3.1.3

Identifiers

CVE-2026-73603
GHSA-8gj2-2cvc-6xx7

Timeline

2026-07-27: disclosed
2026-08-04: advisory
2026-08-04: patched: Fixed in version 3.1.4

References

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