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.
References
| Link | Resource |
|---|---|
| https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-m837-xvxr-vqwg | Mitigation Vendor Advisory |
| https://www.vulncheck.com/advisories/flowise-hardcoded-cors-wildcard-in-tts-endpoint | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-06-30 23:17
Updated : 2026-07-06 15:49
NVD link : CVE-2026-56277
Mitre link : CVE-2026-56277
CVE.ORG link : CVE-2026-56277
JSON object : View
Products Affected
flowiseai
- flowise
CWE
CWE-346
Origin Validation Error
