Medium severity · published Jun 30, 2026
CVE-2026-56277
Flowise - Hardcoded CORS Wildcard in TTS Endpoint
6.5
CVSS
0.2%
EPSS
No
On KEV
Description
Flowise before 3.1.2 sets Access-Control-Allow-Origin to a hardcoded wildcard (*) on its text-to-speech (TTS) generation endpoint (packages/server/src/controllers/text-to-speech/index.ts), independent of the server's configured CORS policy. This bypasses the server's otherwise restrictive default CORS configuration (getCorsOptions()) and allows any webpage to make cross-origin requests that trigger TTS generation using stored credentials, enabling drive-by cross-origin credential abuse.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
Low
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 7% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
FL
Flowise · Flowise
before 3.1.2 · source: vendor, NVD
Affected product
FL
Flowise
Flowise
More from Flowise
9.9
CVE-2026-56274
Flowise - Remote Code Execution via MCP Security Bypass in validateCommandFlags and validateArgsForLocalFileAccess
9.8
CVE-2026-56271
Flowise - Weak Default JWT Secrets in Authentication Middleware
9.8
CVE-2025-71338
Flowise through 2.2.7 - Arbitrary File Write to Remote Code Execution via document-store API
9.8
CVE-2025-71336
Flowise - Unsandboxed Remote Code Execution via Custom MCP
9.8
CVE-2025-71334
Flowise - Arbitrary File Access via Missing Chat Flow ID Validation