API credential abuse via missing TTS authorization
Published Aug 13, 2026 · Updated Aug 13, 2026
Missing authorization in Flowise before 3.1.4 allows remote attackers to consume private chatflow TTS credentials through a public endpoint. The whitelisted generateTextToSpeech controller fetches a chatflow without workspace scoping or an isPublic check, then decrypts its stored OpenAI or ElevenLabs key for the request. Exploitation requires a valid UUID for a private chatflow with TTS enabled and permits unlimited audio generation that consumes the owner's API quota and funds.
Summary
What happened
Missing authorization in Flowise before 3.1.4 allows remote attackers to consume private chatflow TTS credentials through a public endpoint. The whitelisted generateTextToSpeech controller fetches a chatflow without workspace scoping or an isPublic check, then decrypts its stored OpenAI or ElevenLabs key for the request. Exploitation requires a valid UUID for a private chatflow with TTS enabled and permits unlimited audio generation that consumes the owner's API quota and funds.
The record
- CVE
- CVE-2026-73603
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.1.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Embedded curl proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo